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 84736 - crash in free() at nautilus startup
crash in free() at nautilus startup
Status: VERIFIED INCOMPLETE
Product: nautilus
Classification: Core
Component: general
unspecified
Other other
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-06-10 12:44 UTC by tjb
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.0


Description tjb 2002-06-10 12:44:12 UTC 
Package: nautilus
Severity: normal
Version: 2.0.0
Synopsis: Yet another crash at login
Bugzilla-Product: nautilus
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.0)

Description:
Description of Problem:

I updated to the latest snaps this morning, logged out and back in and
everything worked fine. I then read about the happygnome gdm theme,
logged out to try to enable it, and when I logged back in, I got this
crash.

One thing I have noticed is that I only seem to get the hangs/crashes at
login on my dual CPU systems. The single CPU systems rarely have the
problem, if ever.


Additional Information:
Red Hat 7.3/Ximian Gnome 2
Snaps/nautilus2-2.0.0.0.200206100130-0.snap.ximian.1




Debugging Information:

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

[New Thread 1024 (LWP 7405)]
[New Thread 2049 (LWP 7410)]
[New Thread 1026 (LWP 7411)]
[New Thread 2051 (LWP 7412)]
[New Thread 3076 (LWP 7413)]
[New Thread 4101 (LWP 7414)]
[New Thread 5126 (LWP 7415)]
[New Thread 6151 (LWP 7416)]
[New Thread 7176 (LWP 7417)]
[New Thread 8201 (LWP 7418)]
[New Thread 9226 (LWP 7419)]
[New Thread 10251 (LWP 7420)]
0x420b4769 in wait4 () from /lib/i686/libc.so.6

+ Trace 23584

Thread 1 (Thread 1024 (LWP 7405))

  • #0 wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    from /lib/i686/libpthread.so.0
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 620
  • #4 pthread_sighandler
    from /lib/i686/libpthread.so.0
  • #5 <signal handler called>
  • #6 free
    from /lib/i686/libc.so.6
  • #7 _gdk_xsettings_setting_free
    at xsettings-common.c line 152
  • #8 gdk_setting_get
    at gdkevents-x11.c line 2199
  • #9 gtk_settings_get_property
    at gtksettings.c line 301
  • #10 g_object_get_valist
    at gobject.c line 541
  • #11 g_object_get
    at gobject.c line 977
  • #12 _gtk_rc_context_get_default_font_name
    at gtkrc.c line 1294 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-06-10 08:44 -------

Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
Comment 1 Luis Villa 2002-06-11 15:56:59 UTC 
Dave: another nautilus-but-probably-gtk crasher. :/
Comment 2 jacob berkman 2002-06-14 20:42:37 UTC 
bored again
Comment 3 jacob berkman 2002-06-18 21:24:39 UTC 
i couldn't reproduce this (on a SMP machine) with either current
snapshots or the ones you said you had at the time.

do you still get this?

luis, should the be marked as less severe?

it could be just some memory corruption from something else....
Comment 4 Michael Meeks 2002-06-19 12:48:47 UTC 
#84273 is another memory corruption crasher, possibly related
Comment 5 Luis Villa 2002-06-19 19:12:14 UTC 
tjb: do you still see this?
Comment 6 tjb 2002-06-19 19:46:26 UTC 
I'm not sure. Nautilus doesn't seem to crash at login much anymore, it
just hangs most of the time. I have another bug open on that (#84723).
I'd say this one can be closed.