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
Hello, I was debugging the decoding code and get some thought regarding EXT32 format: is it necessary to allocate the table of 2^32-1 bytes ad hoc before reading the rest of the bytes?
What if the data payload will be just few bytes? The allocation is done earlier and over 1GB of memory is used on JVM - that is a waste. Such approach open potential vulnerability on client side of the library that message this kind will be passed. Was such concern was thought earlier? Is it responsibility on the client side to "know" what is he going to decode? Don't know if someone else see this situation in a similiar way.
The text was updated successfully, but these errors were encountered:
Hello, I was debugging the decoding code and get some thought regarding EXT32 format: is it necessary to allocate the table of 2^32-1 bytes ad hoc before reading the rest of the bytes?
What if the data payload will be just few bytes? The allocation is done earlier and over 1GB of memory is used on JVM - that is a waste. Such approach open potential vulnerability on client side of the library that message this kind will be passed. Was such concern was thought earlier? Is it responsibility on the client side to "know" what is he going to decode? Don't know if someone else see this situation in a similiar way.
The text was updated successfully, but these errors were encountered: