Skip to content

Memory allocation in EXT32 #329

Description

@WernherVonData

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions