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 601972 - Devhelp crashes when navigating sidebar with arrow keys
Devhelp crashes when navigating sidebar with arrow keys
Status: RESOLVED DUPLICATE of bug 601048
Product: devhelp
Classification: Applications
Component: General
git master
Other Linux
: Normal critical
: ---
Assigned To: devhelp-maint
devhelp-maint
Depends on:
Blocks:
 
 
Reported: 2009-11-15 14:37 UTC by Sense Hofstede
Modified: 2009-12-09 22:56 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Stacktrace of the crash (4.49 KB, text/plain)
2009-11-15 14:37 UTC, Sense Hofstede 		Details
ThreadStacktrace of the crash (6.09 KB, text/plain)
2009-11-15 14:38 UTC, Sense Hofstede 		Details

Description Sense Hofstede 2009-11-15 14:37:10 UTC 
When navigating the items in the sidebar of Devhelp with the arrow keys, Devhelp will crash reliably after you've went over a few items.

This bug was originally reported against Ubuntu in its bug tracker Launchpad by Gonzalo Panizo: https://launchpad.net/bugs/454264 This bug report contains a lot of information, including a Stacktrace, a ThreadStacktrace, ProcStatus and ProcMaps. I'm attaching the traces.

The version included with the latest release of Ubuntu, Karmic, is 0.23-4.
Comment 1 Sense Hofstede 2009-11-15 14:37:49 UTC 
Created attachment 147769 [details]
Stacktrace of the crash
Comment 2 Sense Hofstede 2009-11-15 14:38:16 UTC 
Created attachment 147770 [details]
ThreadStacktrace of the crash
Comment 3 Fabio Durán Verdugo 2009-11-15 16:17:23 UTC 
paste here the trace

.

+ Trace 219100

Thread 1 (process 2068)

  • #0 queryInfoCallback
    at ../WebCore/platform/network/soup/ResourceHandleSoup.cpp line 845
  • #1 ??
    from /usr/lib/libgio-2.0.so.0
  • #2 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #3 ??
    from /lib/libglib-2.0.so.0
  • #4 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #5 IA__gtk_main
    at /build/buildd/gtk+2.0-2.18.2/gtk/gtkmain.c line 1216
  • #6 main
    at dh-main.c line 296 






Comment 4


Frederic Peters





          2009-11-15 22:14:10 UTC
        



Could you try the latest version from git?






Comment 5


Javier Jardón (IRC: jjardon)





          2009-11-16 16:28:19 UTC
        



From the latest git repo from today:

(gdb) bt




+
Trace
    219131






    

  • 
#0
WebCore::queryInfoCallback(_GObject*, _GAsyncResult*, void*)

    
                from
                /home/torkiano/local/lib/libwebkit-1.0.so.2

    

    • 

  • 
#1
complete_in_idle_cb_for_thread

    
                at /build/buildd/glib2.0-2.22.2/gio/gsimpleasyncresult.c
                  line
                  650

    

    • 

  • 
#2
g_main_dispatch

    
                at /build/buildd/glib2.0-2.22.2/glib/gmain.c
                  line
                  1960

    

    • 

  • 
#3
IA__g_main_context_dispatch

    
                at /build/buildd/glib2.0-2.22.2/glib/gmain.c
                  line
                  2513

    

    • 

  • 
#4
g_main_context_iterate

    
                at /build/buildd/glib2.0-2.22.2/glib/gmain.c
                  line
                  2591

    

    • 

  • 
#5
IA__g_main_loop_run

    
                at /build/buildd/glib2.0-2.22.2/glib/gmain.c
                  line
                  2799

    

    • 

  • 
#6
IA__gtk_main

    
                at gtkmain.c
                  line
                  1217

    

    • 

  • 
#7
main

    
                at dh-main.c
                  line
                  299

    

    • 













Comment 6


Frederic Peters





          2009-11-16 16:46:38 UTC
        



It's most probably a bug in webkit, see https://bugs.webkit.org/show_bug.cgi?id=30163






Comment 7


Sense Hofstede





          2009-11-16 17:00:22 UTC
        



I get the following trace when running git.

(gdb) bt




+
Trace
    219133






    

  • 
#0
queryInfoCallback

    
                at ../WebCore/platform/network/soup/ResourceHandleSoup.cpp
                  line
                  845

    

    • 

  • 
#1
complete_in_idle_cb_for_thread

    
                at /build/buildd/glib2.0-2.22.2/gio/gsimpleasyncresult.c
                  line
                  650

    

    • 

  • 
#2
g_main_dispatch

    
                at /build/buildd/glib2.0-2.22.2/glib/gmain.c
                  line
                  1960

    

    • 

  • 
#3
IA__g_main_context_dispatch

    
                at /build/buildd/glib2.0-2.22.2/glib/gmain.c
                  line
                  2513

    

    • 

  • 
#4
g_main_context_iterate

    
                at /build/buildd/glib2.0-2.22.2/glib/gmain.c
                  line
                  2591

    

    • 

  • 
#5
IA__g_main_loop_run

    
                at /build/buildd/glib2.0-2.22.2/glib/gmain.c
                  line
                  2799

    

    • 

  • 
#6
IA__gtk_main

    
                at /build/buildd/gtk+2.0-2.18.3/gtk/gtkmain.c
                  line
                  1218

    

    • 

  • 
#7
main

    
                at dh-main.c
                  line
                  299

    

    • 








When running the program in GDB it freezes, so you can see the error message at
the top of the document view part, which says: "Error opening the requested
link"
It doesn't matter what documentation you're reading.

The trace does seem to make it more apparent that it is a bug in WebKit. Other error messages I find in the console are:

** (devhelp:21550): DEBUG: NP_Initialize
** (devhelp:21550): DEBUG: NP_Initialize succeeded
OpenOffice path is '../../openoffice'

The first two are repeated often, the third line sparsely.






Comment 8


Jonathon Jongsma





          2009-12-03 20:50:47 UTC
        



Looks like the stack trace matches Bug #601048, so I guess this is probably a dup.






Comment 9


Gustavo Noronha (kov)





          2009-12-09 22:56:14 UTC
        



(In reply to comment #8)
> Looks like the stack trace matches Bug #601048, so I guess this is probably a
> dup.

Definetly.

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