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 348200 - Crash when double-clicking on entry in very large list view.
Crash when double-clicking on entry in very large list view.
Status: RESOLVED DUPLICATE of bug 345300
Product: nautilus
Classification: Core
Component: Views: List View
unspecified
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 351031 446410 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-07-21 00:47 UTC by michaelb
Modified: 2007-06-12 00:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description michaelb 2006-07-21 00:47:41 UTC 
Distribution: Ubuntu 6.06 (dapper)
Package: nautilus
Severity: Normal
Version: GNOME2.14.2 unspecified
Gnome-Distributor: Ubuntu
Synopsis: Crash when double-clicking on entry in very large list view.
Bugzilla-Product: nautilus
Bugzilla-Component: View as List
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:

Nautilus crashed when I attempted to double click on an entry in a very
large (7057 files) list view. The directory was the "cur" directory in a
maildir-format mailbox that was on a DVD-R, and the entry I clicked on
was a mail file.


Steps to reproduce the crash:
1. Open "cur" directory with 7057 items in a list view.
2. Double click on an item.
3. Crash!! (well, at least on one occasion)

Expected Results:
Would have expected the file to be opened in a text editor.

How often does this happen?
Happened once, and then have been unable to reproduce it.

Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225824576 (LWP 4841)]
[New Thread -1227527248 (LWP 4853)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 69489

Thread 1 (Thread -1225824576 (LWP 4841))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/tls/i686/cmov/libc.so.6
  • #5 xdg_mime_dump
    from /usr/lib/libgnomevfs-2.so.0
  • #6 bsearch
    from /lib/tls/i686/cmov/libc.so.6
  • #7 xdg_mime_dump
    from /usr/lib/libgnomevfs-2.so.0
  • #8 gnome_vfs_xfer_delete_list
    from /usr/lib/libgnomevfs-2.so.0
  • #9 gnome_vfs_xfer_delete_list
    from /usr/lib/libgnomevfs-2.so.0
  • #10 gnome_vfs_xfer_delete_list
    from /usr/lib/libgnomevfs-2.so.0
  • #11 gnome_vfs_mime_type_get_equivalence
    from /usr/lib/libgnomevfs-2.so.0
  • #12 nautilus_file_is_mime_type
  • #13 nautilus_file_is_mime_type
  • #14 fm_directory_view_can_zoom_out
  • #15 fm_directory_view_pop_up_location_context_menu
  • #16 fm_directory_view_pop_up_location_context_menu
  • #17 fm_directory_view_update_menus
  • #18 fm_directory_view_update_menus
  • #19 g_main_context_is_owner
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #21 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #23 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 POA_Nautilus_MetafileFactory__fini
  • #25 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #26 ??
  • #0 __kernel_vsyscall 




------- Bug created by bug-buddy at 2006-07-21 00:47 -------
Comment 1 Baptiste Mille-Mathias 2006-07-21 01:29:54 UTC 
Thanks for the bug report. Without a stack trace from the crash it's very hard to determine what caused it.
Can you provide us with one? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 2 michaelb 2006-07-21 01:54:29 UTC 
When you say you need a stack trace, you mean you need one with debug symbols, right? As it would seem to me that Bug Buddy has already attached a stack trace for me, but one that is missing the debug symbols...

If that is what you want I'll try to get you one, but I'm not too sure if I'll be able to manage it -- since my initial attempt to reproduce the crash did not succeed, the chances of securing a stack trace from the crash are looking slim.
Comment 3 Brent Smith (smitten) 2006-07-22 17:04:09 UTC 
yes, we need debugging symbols - the stack trace you have provided is only marginally useful without them :^)
Comment 4 Fabio Bonelli 2006-08-12 15:05:50 UTC 
*** Bug 351031 has been marked as a duplicate of this bug. ***
Comment 5 Christian Kirbach 2006-08-29 21:37:19 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.
please answer the questions there

*** This bug has been marked as a duplicate of 345300 ***
Comment 6 Pedro Villavicencio 2007-06-12 00:19:59 UTC 
*** Bug 446410 has been marked as a duplicate of this bug. ***