Skip to content
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

Laufhelden failed on long ride #45

Closed
piggz opened this Issue Jan 7, 2018 · 7 comments

Comments

Projects
None yet
4 participants
@piggz
Copy link
Contributor

piggz commented Jan 7, 2018

Went for a long (4+ hours) ride using Laufhelden.

When I finished and went to safe the ride, I found that Laufhelden had crashed and I had a blank cover window.

When opening again, laufhelden told me I had an activity in progress and offered to restore it. I chose yes, but then laufhelden hung, and lipstick gave the 'app has stopped responding' option. I chose to wait a few times, but it never started up.

Perhaps the ride was too long and took too much memory? Possible memory leak?

@jdrescher2006

This comment has been minimized.

Copy link
Owner

jdrescher2006 commented Jan 7, 2018

Do you still have the autosave file? Can you send it to me?

@piggz

This comment has been minimized.

Copy link
Contributor Author

piggz commented Jan 7, 2018

Yes and yes .... what is its location?

@pfbach

This comment has been minimized.

Copy link

pfbach commented Jan 7, 2018

Had the same problem yesterday. Went on a 2-3 hours cross country skiing tour, it crashed when I tried to save it. Unfortunately, I don't think my autosave file survived.

@jdrescher2006

This comment has been minimized.

Copy link
Owner

jdrescher2006 commented Jan 8, 2018

I had the same problem yesterday while a long run of 27km. After 20km the app crashed. Autosave could not be restored.
Seems like I messed it up somehow. Will start debugging asap.

@jdrescher2006

This comment has been minimized.

Copy link
Owner

jdrescher2006 commented Jan 8, 2018

So there are at least two bugs. I found and fixed the one preventing to load the autosave. It has to do with the new map plugin. The other bug may be based on the same problem.

@rinigus

This comment has been minimized.

Copy link

rinigus commented Jan 8, 2018

I'll be checking whether it's caused by mapbox gl plugin at rinigus/mapbox-gl-qml#28. Linking the issues for now

@jdrescher2006

This comment has been minimized.

Copy link
Owner

jdrescher2006 commented Jan 15, 2018

So this should be solved with release v0.9.9-1. Please test and report if you still have problems!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.