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 170572 - crash when asking for properties of larghe file (2.5 GB
crash when asking for properties of larghe file (2.5 GB
Status: RESOLVED DUPLICATE of bug 151024
Product: nautilus
Classification: Core
Component: File and Folder Operations
unspecified
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-03-16 15:45 UTC by de.eik
Modified: 2005-03-16 17:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description de.eik 2005-03-16 15:45:47 UTC
Distribution: Fedora Core release 3 (Heidelberg)
Package: nautilus
Severity: normal
Version: GNOME2.8.0 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: crash when asking for properties of larghe file (2.5 GB
Bugzilla-Product: nautilus
Bugzilla-Component: File and Folder Operations
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:
when asking the properties of a large iso file (+ 2.5 GB) I just
downloaded nautilus crashed

Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?

1
Additional Information:



Debugging Information:

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

(no debugging symbols found)...Using host libthread_db library
"/lib/tls/libthread_db.so.1".
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...[Thread debugging using libthread_db enabled]
[New Thread -1209025920 (LWP 6175)]
[New Thread -1223365712 (LWP 6183)]
[Thread debugging using libthread_db enabled]
[New Thread -1209025920 (LWP 6175)]
[New Thread -1223365712 (LWP 6183)]
[New Thread -1223099472 (LWP 6182)]
[New Thread -1222833232 (LWP 6181)]
[New Thread -1222566992 (LWP 6180)]
[New Thread -1222300752 (LWP 6179)]
[New Thread -1221641296 (LWP 6178)]
[New Thread -1211151440 (LWP 6176)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...[Thread
debugging using libthread_db enabled]
[New Thread -1209025920 (LWP 6175)]
[New Thread -1223365712 (LWP 6183)]
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...(no debugging symbols
found)...(no debugging symbols found)...0x003227a2 in _dl_sysinfo_int80
() from /lib/ld-linux.so.2

Thread 8 (Thread -1211151440 (LWP 6176))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 poll
    from /lib/tls/libc.so.6
  • #2 g_main_context_acquire
    from /usr/lib/libglib-2.0.so.0
  • #3 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #4 link_thread_io_context
    from /usr/lib/libORBit-2.so.0
  • #5 ??
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
  • #7 g_static_private_free
    from /usr/lib/libglib-2.0.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-16 10:45 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "nautilus".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was de.eik@xs4all.nl.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Elijah Newren 2005-03-16 17:20:10 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.

Matches the stack trace in bug 168294, which has been marked as a duplicate of
151024.

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