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
Various crashes during usage #4491
Comments
A lot of actions seem to lead to a crash. Does not seem to be reproducible but seems depending on the speed I perform some actions. |
Back at home and here is the log:
|
@samueltardieu rxjava? |
Yup, it looks like your rotation sensor delivers values very rapidly, much more rapidly that they could be used, and filled the buffer. This could only appear now that we switched to RxJava 1.0 (which includes back pressure). I'll tend to it. |
It make c:geo unusable on my device (Galaxy S4) currently. Seems more devices could suffer from that then. |
On Samsung Galaxy S4 it looks like the rotation sensor delivers events faster than cgeo can handle them during some lists operations (in SENSOR_DELAY_NORMAL mode). Part of work on #4491.
There is no need to update the arrow display in list more than 4 times per second, as this is not an instrument for precise cache hunting. Part of work on #4491.
@Lineflyer Please confirm that this fixes the issue for you (starting with 20141124-NB). I have put in place both a protection against a buffer fill in orientation and rotation providers, and also limited the orientation and location updates to 4 per second in lists as there is no need to be more precise than that. |
Version 20141124-NB seems to be stable again. No more crashes during usage up to now. |
With todays NB
Details later
The text was updated successfully, but these errors were encountered: