yelp_document_get_page: assertion failed: (document != NULL && YELP_IS_DOCUMENT (document)) Aborted (core dumped)

Bug #218537 reported by bzmay
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
yelp (Ubuntu)
Incomplete
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: yelp
Applies to 8.04 and 7.10

Install glibc-doc
Start yelp

Select Advanced Topics->GNU Info Pages->Software Libraries->Libc

This will cause a crash and an error:
**
** Yelp:ERROR:(yelp-document.c:217):yelp_document_get_page: assertion failed: (document != NULL && YELP_IS_DOCUMENT (document))
Aborted (core dumped)

This can also happen when clicking on some other Info node and clicking on hyperlinks inside of yelp info viewer plugin (although the glibc node is more likely to crash - probably due to its size). It seems that the lower position in the list of yelp GNU-Info topic, the greater likelihood of a crash. Once a crashing node is found, all the nodes below it will also crash. So it is like a snowball effect where one bad apple spoils everything below it.

ProblemType: Crash
Architecture: i386
Date: Thu Apr 17 01:24:25 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/yelp
Package: yelp 2.22.1-0ubuntu2
PackageArchitecture: i386
ProcCmdline: yelp
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: yelp
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: yelp crashed with SIGSEGV
Uname: Linux 2.6.24-16-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Tags: apport-crash
Revision history for this message
bzmay (bogzak) wrote :
bzmay (bogzak)
description: updated
description: updated
Revision history for this message
bzmay (bogzak) wrote :

I am attaching another coredump as I am not sure if the original one attached was from the repro steps that I listed.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

please do not attach .crash files to the report. Apport will pickup your report and automatically retrace with the CoreDump.gz file available on it, there's no need for extra files for now. Thanks you.

bzmay (bogzak)
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in yelp:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug is waiting for retracing rather, changing to new

Changed in yelp:
status: Incomplete → New
Revision history for this message
burgwinkel (burgwinkel) wrote :

This may be unimportant, but the crash was not identical under gdb as when yelp was run directly. Specifically the window did not vanish, but merely froze and became totally unresponsive.

Revision history for this message
bzmay (bogzak) wrote :

Now the error is different: ***MEMORY-ERROR***: yelp[6915]: GSlice: assertion failed: sinfo->n_allocated > 0
This is from 8.04 release, bug report was from 8.04 beta.

burgwinkel, gdb stops the program at the moment of the crash, so the window cannot repaint itself. If you type "continue", the crash will run its course and the behavior will be identical.

Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:malloc_consolidate () from /lib/tls/i686/cmov/libc.so.6
_int_malloc () from /lib/tls/i686/cmov/libc.so.6
malloc () from /lib/tls/i686/cmov/libc.so.6
PR_Malloc (size=3619) at prmem.c:467
PL_ArenaAllocate (pool=0x951ba88, nb=16) at plarena.c:228

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Could you try to reproduce the same with Ubuntu 8.10 or 9.04? Thanks in advance.

Changed in yelp:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in yelp:
status: Incomplete → Invalid
Revision history for this message
Bo Stenhols (bo-stenhols) wrote :

How do I get around the problem that the system stops when browsing from a open office or audicity program? Obviously, leting the file find the program is working allright.

Revision history for this message
marco.pallotta (marco-pallotta) wrote :

Tested with Intrepid but yelp goes in segmentation fault at the moment that I search any word in the "search form".
I will try it in Jaunty as soon as possible.

Changed in yelp (Ubuntu):
status: Invalid → Incomplete
Revision history for this message
antonioni (antonioni-rocha) wrote :

Example of reproduction of this bug (in Ubuntu 9.04):

. In Yelp, try find 'samba'; the list of results will be shown;
. In the list of results, select the second result ('Administrative Tasks'); Yelp becomes to the state 'Loadind...', and nothing happens;
. click other time in the second result ('Administrative Tasks'). The Yelp crashes and the message in the terminal is shown in the image attached.

Revision history for this message
antonioni (antonioni-rocha) wrote :

Coincidentally I have found this bug confirmed in the Launchpad:
https://bugs.launchpad.net/yelp/+bug/220142

It has the same problem of here.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.