-
Notifications
You must be signed in to change notification settings - Fork 647
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
Null pointer exception during instruction 'monitor-enter v0' #81
Comments
Same issue here on Android 6.0.1 device. 1st type of crash report
and
I'm using. It puzzles me that the available() method seems to interact with Shell.threaded. This should not be the behaviour as far as I can read from the code. I suspect that this might be related to some kind of threading / synchronization error. |
Need minimal code to reproduce and as much device info as possible. If you're not using Interactive/Threaded mode anyway, you might be able to work around the issue for now by calling It's certainly strange though, the synchronizer at the quoted line should never be |
Unfortunately I'm unable to reproduce this yet. I have set the following NewBuilderListener. Could this be related to the issue?
I can see that the affected device keeps crashing (500 + times) Our code do make use of Threaded mode for some other calls. I fear that this issue could occur for these calls as well.. |
Reading up some more, the only reason I can come up with for the synchronizer causing an NPE (as you can read in the code its a final member of the I think that would be relatively easy to test (and fix), but we need a testable case first. I have some ideas on how to make one. I do not believe your |
Also any info about the specific device, firmware, root app and version, is welcome. |
Great to hear that there might be a way ahead! I have the following information on the device: Is there anything else I can do or more exact information I can provide? Thank you so much for all your hard work on superSU and in the community! I hope you and your family are safe during all this. |
I pushed a new version, you may see if that works: See 5005486 |
Cool! I'll give it a spin. |
It looks good. I have still not been able to get access to the device that was showing the issue and thus cannot verify the fix completely. I hope to be able to do so soon an will inform you then. Thank you. |
Some Android 5.0 and 5.1 devices produce NPE with the latest libsuperuser. However I'm not sure what exactly triggers these NPEs.
implementation 'eu.chainfire:libsuperuser:1.1.0.+'
The text was updated successfully, but these errors were encountered: