After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 358489 - crash in Help: clicking around
crash in Help: clicking around
Status: RESOLVED DUPLICATE of bug 318996
Product: yelp
Classification: Applications
Component: General
2.16.x
Other All
: High critical
: ---
Assigned To: Yelp maintainers
Yelp maintainers
Depends on:
Blocks:
 
 
Reported: 2006-09-30 12:42 UTC by Dimitur Kirov
Modified: 2006-09-30 13:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
same trace + yeld, compiled with debug flags (20.68 KB, text/plain)
2006-09-30 13:52 UTC, Dimitur Kirov
Details

Description Dimitur Kirov 2006-09-30 12:42:07 UTC
Version: 2.16.0

What were you doing when the application crashed?
clicking around


Distribution: Gentoo Base System version 1.12.5
Gnome Release: 2.16.0 2006-09-28 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 207405056 vsize: 0 resident: 207405056 share: 0 rss: 60125184 rss_rlim: 0
CPU usage: start_time: 1159619885 rtime: 0 utime: 918 stime: 0 cutime:865 cstime: 0 timeout: 53 it_real_value: 0 frequency: 2

Backtrace was generated from '/usr/bin/yelp'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208850768 (LWP 16834)]
[New Thread -1354179680 (LWP 16846)]
[New Thread -1345786976 (LWP 16845)]
[New Thread -1337394272 (LWP 16844)]
[New Thread -1329001568 (LWP 16843)]
[New Thread -1320322144 (LWP 16839)]
[New Thread -1233757280 (LWP 16838)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1208850768 (LWP 16834))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/libc.so.6
  • #5 ??
  • #6 ??
  • #0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-09-30 12:49:36 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Can you reproduce this, Dimitur?
Comment 2 Dimitur Kirov 2006-09-30 13:52:14 UTC
Created attachment 73704 [details]
same trace + yeld, compiled with debug flags

I managed to reproduce it several times. All you have to do is click fast. Well, I suppose that overloading the computer with some cpu and disk expensive tasks will make it easier to reproduce.

On the home page there are ten categories. 
# Accessories
# Games
# Graphics
# Internet
# etc....
I don't know the exact name, but let's call them 'Main Categories'

Steps to reproduce.
1. Click on one of the main categories:'Accessories'

2. Click on some of the links on the right: 'Archive Manager Manual'
Now a side panel is shown and all main categories are moved about 200px right.

3. Before page is fully loaded click on some of the main categories: 'Games'



here are the last lines of console output (firefox is build with debug flags too). I hope that they can provide some additional info:
###!!! ASSERTION: reflow dirty lines failed: 'NS_SUCCEEDED(rv)', file nsBlockFrame.cpp, line 903
Break: at file nsBlockFrame.cpp, line 903
nsBlockReflowContext: Block(body)(1)@0xa368080 metrics=-559038737,-559038737!
nsBlockReflowContext: Block(body)(1)@0xa368080 didn't set whad -559038737,-559038737,-559038737,-559038737!
###!!! ASSERTION: reflow dirty lines failed: 'NS_SUCCEEDED(rv)', file nsBlockFrame.cpp, line 903
Break: at file nsBlockFrame.cpp, line 903
--DOMWINDOW == 6
WARNING: unknown protocol in nsScriptSecurityManager::CheckLoadURI, file nsScriptSecurityManager.cpp, line 1394
WARNING: unknown protocol in nsScriptSecurityManager::CheckLoadURI, file nsScriptSecurityManager.cpp, line 1394
++DOMWINDOW == 7
WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(result)) failed, file nsXMLContentSink.cpp, line 1001
WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(result)) failed, file nsXMLContentSink.cpp, line 1001
WARNING: NS_ENSURE_TRUE(rootElem) failed, file nsXMLPrettyPrinter.cpp, line 166
Comment 3 Don Scorgie 2006-09-30 13:57:33 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 318996 ***