-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
VNCConnService race crashes #172
Comments
Still with 2.0.2, it's not a race. May it be https://stackoverflow.com/questions/23148677/service-onstartcommand-throwing-nullpointerexception ? Also see bk138/droidVNC-NG@44765cf 🤔 |
One issue might be the data type for multivnc/android/app/src/main/java/com/coboltforge/dontmind/multivnc/VNCConnService.kt Line 90 in 2aa9abe
Because |
You mean that's the reason it reports line 2 deep from the bowels of Kotlin instead of the line of onStartCommand()? |
re #172 And most specifically #172 (comment) which states "Because Intent is used instead of Intent?, Kotlin compiler will automatically insert a null-check here. But intent parameter can be null for onStartCommand()."
re #172 And most specifically #172 (comment) which states "Because Intent is used instead of Intent?, Kotlin compiler will automatically insert a null-check here. But intent parameter can be null for onStartCommand()."
It might be.
|
Yeah those details are ommited by the Goog Play stack trace above 🙄 |
No more reports incoming on Google Play, I rule this issue closed 🔨 |
VNCConnService is still racy, sometimes NullpointerExceptions can occur.
Reported backtraces are not really helpful:
Theories
The text was updated successfully, but these errors were encountered: