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 603394 - Crash when typing a research too fast
Crash when typing a research too fast
Status: RESOLVED DUPLICATE of bug 601048
Product: devhelp
Classification: Applications
Component: General
unspecified
Other Linux
: Normal normal
: ---
Assigned To: devhelp-maint
devhelp-maint
Depends on:
Blocks:
 
 
Reported: 2009-11-30 17:05 UTC by Olivier Le Thanh Duong
Modified: 2009-11-30 17:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Olivier Le Thanh Duong 2009-11-30 17:05:05 UTC 
When I type my search too fast it crash, I think it's linked with the fact that it reload the page each time I type a letter even if it's already on the right one.

+ Trace 219378

  • #0 queryInfoCallback
    at ../WebCore/platform/network/soup/ResourceHandleSoup.cpp line 845
  • #1 IA__g_simple_async_result_complete
    at /build/buildd/glib2.0-2.22.2/gio/gsimpleasyncresult.c line 588
  • #2 complete_in_idle_cb_for_thread
    at /build/buildd/glib2.0-2.22.2/gio/gsimpleasyncresult.c line 650
  • #3 g_idle_dispatch
    at /build/buildd/glib2.0-2.22.2/glib/gmain.c line 4065
  • #4 g_main_dispatch
    at /build/buildd/glib2.0-2.22.2/glib/gmain.c line 1960
  • #5 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.22.2/glib/gmain.c line 2513
  • #6 g_main_context_iterate
    at /build/buildd/glib2.0-2.22.2/glib/gmain.c line 2591
  • #7 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.22.2/glib/gmain.c line 2799
  • #8 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 ??
  • #10 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #11 ?? 






Comment 1


Frederic Peters





          2009-11-30 17:08:37 UTC
        



Most certainly a Webkit issue, and one I believe is fixed in master.

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