App doesn't respond after loading a complex route #638
Replies: 12 comments 55 replies
-
@WolfgangZ42 Thanks for the report. I cannot reproduce it using your profile and route example. How do you import the route? |
Beta Was this translation helpful? Give feedback.
-
I had this issue with the frozen Cruiser app again after loading today's "Cruiser 5 test"-route!!!
Should I send you the route in question and the profile I used @devemux86? |
Beta Was this translation helpful? Give feedback.
-
Questions to both @WolfgangZ42 and @bios4:
|
Beta Was this translation helpful? Give feedback.
-
The problem is probably with the automatic map zoom / scroll to show the whole imported route. I will think how we can solve this. If you keep the map at same area / zoom after import a complex route. But if at the 1st step, move / zoom to a completely different map area. |
Beta Was this translation helpful? Give feedback.
-
Please try the latest Beta 26. |
Beta Was this translation helpful? Give feedback.
-
Please try the latest Beta 27. |
Beta Was this translation helpful? Give feedback.
-
Import route displays "Show whole route" prompt after import in Cruiser 5.0.1-b8: |
Beta Was this translation helpful? Give feedback.
-
B9: On a 200 km tour four times "App not responding". However, this time it didn't crash and I was able to continue riding. Could it be that the average speed is reset after each app restart? I don't think that's ideal. It would be better to reset it manually as before. |
Beta Was this translation helpful? Give feedback.
-
b10: still 3 times on a 100km Tour, the Message appears : |
Beta Was this translation helpful? Give feedback.
-
This is a very personal route from which you can read my home town, so I don't want to do that. I drive it 2-3 times a week. But it also happens on other routes. It could happen if you deliberately deviate from the planned route and a recalculation takes place and you don't adjust the route immediately by skipping it. Then a multiple recalculation takes place. Could this take too long and result in timeouts? The app no longer crashes, but the message disappears again after approx. 10 to 15 seconds. So it is not that critical. It's just a slight blur. And I still drive more often with V4. But it only happens with V5.0.1 bXX, actually b10. It is also possible that it happens when routes cross each other, just an assumption. Next Sunday, for example, I'm driving a tour that I could send if it happens again. It is a non-intersecting route. I will use V4 and V5 in parallel to see what happens. By the way, could the reset of the average speed be optional on every closure of the app? I often close the app in pauses, but want to keep the average speed of the whole trip. Or was it a wish of a user to reset this every time automatically? |
Beta Was this translation helpful? Give feedback.
-
Cruiser 5.0.2-b1 contains changes trying to solve the not responding report. @WolfgangZ42 @bios4 Can you test this version? (the previous version is available in Releases, if you want to restore it) |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
When I load a relatively complex route, it often happens that Cruiser no longer responds.
The route is loaded - the info box pops up, but a few seconds later the corresponding display appears.
. . .
After “Close app” and calling up Cruiser again, the route is loaded correctly. Here is an example route and my profile: Example.zip - I hope you can reproduce it.
Beta Was this translation helpful? Give feedback.
All reactions