-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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
java.lang.OutOfMemoryError: Could not allocate JNI Env #6283
Comments
It has happened again, but on a different device and with a different user and with an unmodified signal: https://gist.github.com/anonymous/b4bf8bb05611b0c42a75aaac8ae130d6 Nothing extraordinary happened, except that the device received a lot of receipts before it crashed. |
New OkHttpClients came with their own thread and connection pools. With newBuilder() we can create a new client with an already existing pool. Fixes signalapp/Signal-Android#6283
i think i found the culprit! |
was this fixed by signalapp/libsignal-service-java@0557122? |
GitHub Issue Cleanup: |
I have:
Bug description
Out of the blue, signal crashed.
Pretty sure this is not related to my build, and the device had (after the crash) ~1.5GB free ram. An issue on so linked this error messages to leaked file descriptors, which is apparently intended in libsignal. The libsignal version i use has fixed that issue, but maybe there are other leaked FDs?
Steps to reproduce
Device info
Device: Xiaomi Redmi Note 3 Pro
Android version: 6.0.1
Signal version: 3.29.6 + Trolldemorted@cdb8ac2
Link to debug log
https://gist.github.com/anonymous/51447caee0494fef9bb45994cd4fada3
The text was updated successfully, but these errors were encountered: