-
Notifications
You must be signed in to change notification settings - Fork 645
OutOfMemoryError happens when try to decode the wrong ByteArray #2649
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Similar problem in CBOR: https://youtrack.jetbrains.com/issue/KT-66282/Serialization-flaky-OutOfMemoryError-with-Cbor |
Thanks, reproduced on 1.9.21 + 1.6.3, too |
…criptor Also optimized skipping of size delimited fields - removed the creation of an byte array in case of skipping Fixes #2649
…criptor Also optimized skipping of size delimited fields - removed the creation of an byte array in case of skipping Fixes #2649
@sandwwraith This problem still occurs, I am using the latest version "1.8.0"
|
Hi all. it is still occurs. please reopen the issue @sandwwraith @sang-eun @shanshin |
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
Sometimes our server get wrong ByteArray. We hoped the server throw wrong format error immediately when we try to decode the message. However, protobuf decoder blocks until java heap space out of memory error happens.
From our debugging, message is keep pushBacked by
reader.pushBackTag()
and index never moves forward from this method.To Reproduce
// result
Expected behavior
throw wrong format error immediately.
Environment
The text was updated successfully, but these errors were encountered: