You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a creative (mis)use of EASY_BLOCK we are adding additional diagnostic data to some blocks in debug builds, sometimes this can be a long HTTP response for instance. In one such case we discovered that a buffer overrun was occurring.
The implicit block name limit didn't appear to be documented anywhere, but in addition to documentation perhaps it could be truncated by easy_profiler as well.
The text was updated successfully, but these errors were encountered:
Hello! Sorry for long time silence. Thank you for feedback.
Quick investigation shows that about long name (3k length) for block cause crash =( It's seem to be a bug.
Memory for the blocks is allocating with chunks of fixed length, this is done for optimization reasons.
Really long name has exceed the size of the chunk which lead to crash - that's the reason.
Definitely, we should truncate such names automatically to prevent crashes.
As for additional diagnostic information, I would better suggest you to use EASY_VALUE blocks to store custom variables and data.
[core] #157 added new build flag EASY_OPTION_TRUNCATE_RUNTIME_NAMES which will prevent from crash for very big block names, but will reduce performance. Disabled by default because of very rare use case;
[core] #157 added new build flag EASY_OPTION_CHECK_MAX_VALUE_SIZE for EASY_VALUE arrays and strings - same as the flag above for block names. Also disabled by default;
In a creative (mis)use of EASY_BLOCK we are adding additional diagnostic data to some blocks in debug builds, sometimes this can be a long HTTP response for instance. In one such case we discovered that a buffer overrun was occurring.
The implicit block name limit didn't appear to be documented anywhere, but in addition to documentation perhaps it could be truncated by easy_profiler as well.
The text was updated successfully, but these errors were encountered: