Frequent segmentation faults
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
LottaNZB |
Confirmed
|
High
|
LottaNZB Development Team |
Bug Description
Some users, including myself, experience regular crashes with various stack traces like the following. They are the main reason why the release of LottaNZB 0.6 has been delayed for such a long time. It seems like the bug has still not been resolved.
Unfortunately, I don't have any clue about the underlying cause and debugging is hard because they occur in the middle of the downloading process. The fact that they originate from the low-level library GDK makes things even worse. I wonder whether there's a problem in LottaNZB's code that cause the API of GDK to be used in an invalid way or whether there's actually a bug in GDK.
Attempts have been made to ensure that the GTK lock is acquired whenever GUI-related code is executed, but this measure has either not been thorough enough or the bug caused by something completely different.
/home/todd/
gtk.main()
**
Gdk:ERROR:
Changed in lottanzb: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → LottaNZB Development Team (lottanzb) |
milestone: | none → 0.6 |
Changed in lottanzb: | |
milestone: | 0.6 → 0.6.1 |
summary: |
- Crashes due to Gdk:ERROR...miUnionNonO: assertion failed: (y1 < y2) + Frequent segmentation faults |
description: | updated |
Unless someone comes up with a solution sooner, I'll try to pinpoint the crash to an operation performed by LottaNZB (if possible) and maybe obtain a proper stacktrace using gdb. After having done a web search, it seems to me that LottaNZB is definitely not the only application affected by this mysterious bug, but I haven't seen any solutions so far.