Opened 7 years ago

Closed 5 years ago

#1320 closed defect/bug (Incomplete/Missing infos)

random crashes when scrolling map

Reported by: rico (2) Owned by: KaZeR
Priority: major Milestone:
Component: core Version: git master
Severity: normal Keywords:



navit randomly crashes when scrolling the map over big distances. It seems, in function event_glib_call_timeout_single in event_glib.c sometimes an invalid timerevent gets removed.


Change History (3)

comment:1 Changed 7 years ago by sleske

Thank you for your report. Could you provide some more details?

  • On what OS/platform does this happen?
  • Which graphics plugin do you use? (<graphics type="XXX"/> in navit.xml)
  • Which SVN/Git version did you use? You can see that in the "About" menu.
  • Could you run the program under gdb and provide a backtrace of the crash?

Also, could you provide a way to reproduce the problem? Ideally, upload the navit.xml and the map file somewhere (do not attach it here, as it will probably be too big).

comment:2 Changed 7 years ago by rico (2)

It happens at least on Debian armhf and amd64 with qt_painter and gtk_drawing_area, but I forgot to mention, only if the device has a gps fix. I'm always using the latest svn/git version, but the problem is there for months.

The strange thing is, with gdb the problem isn't reproducable. And another one: On every there are different error messages (from glibc). The most common error message is "smallbin double linked list corrupted".

My config is split into several parts:

comment:3 Changed 5 years ago by sleske

  • Resolution set to Incomplete/Missing infos
  • Status changed from new to closed

With the information available I have not been able to reproduce the problem. Since this ticket is quite old, I'm closing it.

Feel free to reopen if you can provide more information. In particular, a backtrace would be helpful. If you cannot reproduce the problem runnign under gdb, you can enable core files with the command "ulimit -c unlimited". Then Navit will leave behind a corefile if it crashes, which you can analyse with gdb after the crash.

Note: See TracTickets for help on using tickets.