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

Crash when uploading GPS trace to OSM #115

Closed
M-Reimer opened this issue Feb 21, 2021 · 3 comments
Closed

Crash when uploading GPS trace to OSM #115

M-Reimer opened this issue Feb 21, 2021 · 3 comments

Comments

@M-Reimer
Copy link

We already had this in #98 and now I have the same problem again.

Uploading a GPS trace seems to succeed but then Viking disappears and on console I have:

free(): double free detected in tcache 2
@rnorris
Copy link
Collaborator

rnorris commented Feb 21, 2021

I can't readily reproduce this issue with the latest code.

Can you please confirm a few details please which can help in diagnosing the problem:

  • That you using the latest code (v1.8 hasn't been updated to include the fix in Crash when uploading GPS trace to OSM #98)
  • What style of OSM authentication is being used (OAuth or OSM Username+Password)?
  • Is the track GPX v1.0 or v1.1?
  • And finally, if the GPX Upload is made a publically viewable OSM Track - and if you don't mind - could you please provide a link to the successful upload.

Further if you are compiling from source, you can modify the file osm-traces.c at around line 482;
if you stop the command to perform the actual upload, you might be able to reproduce the error on your system and potentially capture a debugger backtrace to capture what is happening.
Change:

res = curl_easy_perform(curl);

-->

res = CURLE_OK;

As then you can instigate upload actions in the program without it actually uploading to OSM - this is what I do for testing.

@M-Reimer
Copy link
Author

I'm using the latest release. Actually I expected that after 7 months the fix could have landed in a bugfix release so it actually is usable for the average user.

Any plans when a release could happen?

@rnorris
Copy link
Collaborator

rnorris commented Feb 24, 2021

@M-Reimer - Hopefully a new release will be done by the end of March.

@rnorris rnorris closed this as completed Feb 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants