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
You can employ 2 tactics:
a) You can specify a custom allocator that will not return inputs beyond a certain size.
b) You can instantiate a reader and choose to only read a certain number of bytes from the input and bound the resource usage that way.
I believe it should not use more than a fixed size based on the window size, but you can ensure that using (a)
And since the reader or writer interfaces only use bounded buffers you can either stop when your output is full or keep streaming it.
Can untrusted inputs be decompressed without using unbounded memory?
The text was updated successfully, but these errors were encountered: