GNOME Bugzilla – Bug 105266
yelp crashed
Last modified: 2004-12-22 21:47:04 UTC
Package: Yelp Severity: normal Version: 2.2.0 Synopsis: yelp crashed Bugzilla-Product: Yelp Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: yelp crashed Steps to reproduce the problem: 1. open app preferences capplet 2. click on Help 3. click on web browser preferences Debugging Information: Backtrace was generated from '/usr/bin/gnome-help' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 1932)] [New Thread 32769 (LWP 1943)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x40954a39 in wait4 () from /lib/libc.so.6
+ Trace 33495
Thread 1 (Thread 16384 (LWP 1932))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-04 22:28 ------- Reassigning to the default owner of the component, micke@codefactory.se.
Looks like a crasher in libgtkhtml. I cannot reproduce with yelp-2.2.0 and libgtkhtml-2.2.0. Can you describe in more detail exactly what you did to produce the crash and if it's reproducable?
I tried it again. I opened the gnome-default-applications-properties capplet, and clicked the Help button. It shows the "Loading..." page. Much disk activity later, the same thing happened (segfault). This time, however, I noticed that mozilla died again, and my suspicions were confirmed when I looked in /var/log/syslog: ... Feb 5 18:18:17 imp kernel: Out of Memory: Killed process 1985 (mozilla-bin). Feb 5 18:18:17 imp kernel: Out of Memory: Killed process 1987 (mozilla-bin). Feb 5 18:18:17 imp kernel: Out of Memory: Killed process 2584 (mozilla-bin). Feb 5 18:18:17 imp kernel: Out of Memory: Killed process 3094 (yelp-db2html). I waited a bit, then clicked the Help button again, and, after a while, the same thing happened. Just a little after the crash, "free -m" reported: total used free shared buffers cached Mem: 56 41 14 0 1 16 -/+ buffers/cache: 23 32 Swap: 109 36 73 which means that, from full memory usage (inc swap), a lot gets freed when yelp-db2html is forcibly killed: approximately 87MiB. (Which implies that yelp-db2html was using that much RAM!) But anyhow, it seems that when yelp-db2html dies, something causes yelp to segfault.
This looks like a new stack trace.
Hmm .. sounds like a leak + an infinite loop. Wonder if it's in Yelp or Gtkhtml2 (or yelp-db2html) :(
*** Bug 106026 has been marked as a duplicate of this bug. ***
The function in which the crash occurs is html_box_get_containing_block_width is in Gtkhtml2. Looking at the code in that function it is hard to figure out what could cause the crash. There is not enough information here to determine the cause of the crash.
*** Bug 129646 has been marked as a duplicate of this bug. ***
Not reproducible with yelp 2.5.5 and libgtkhtml 2.5.3. May be closed?
Mass moving Yelp bugs to new maintainer.
Yes, closing.