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 100460 - Gedit crashes when ran
Gedit crashes when ran
Status: RESOLVED DUPLICATE of bug 95063
Product: gedit
Classification: Applications
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Gedit maintainers
gedit QA volunteers
Depends on:
Blocks:
 
 
Reported: 2002-12-05 20:34 UTC by pvinson
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description pvinson 2002-12-05 20:32:56 UTC 
Package: gedit
Severity: normal
Version: 2.0.2
Synopsis: Gedit crashes when ran
Bugzilla-Product: gedit
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:
    Gedit seems to be crashing after computer has been running so many
days.  Usually gedit crashes after the computer has been running for
least 2 days.  I get an additional error with the crash error.  The
other one states that an error occurred while loading or saving
configuration information.  Maybe this is a Gconf problem?

Steps to reproduce the problem:
1.  Have computer run least 2 days
2.  Run Gedit, does always work right away.  Seems to be random
3. 

Actual Results:


Expected Results:


How often does this happen?
  

Additional Information:
  This never happened when I was using the lastest Gnome from gnome.org while I was still using Red Hat Linux 7.3.  This problem started when I installed Red Hat Linux 8.0.  I don't know if that has anything to do with it, but you never know.



Debugging Information:

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

(no debugging symbols found)...[New Thread 8192 (LWP 2319)]
0x420ae169 in wait4 () from /lib/i686/libc.so.6

+ Trace 31370

Thread 1 (Thread 8192 (LWP 2319))

  • #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_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #4 __pthread_sighandler
    from /lib/i686/libpthread.so.0
  • #5 <signal handler called>
  • #6 gconf_client_get_string_with_default
  • #7 gedit_prefs_manager_get_string
  • #8 gedit_prefs_manager_get_toolbar_buttons_style
  • #9 gedit_window_prefs_new
  • #10 gedit_mdi_app_created_handler
  • #11 g_cclosure_marshal_VOID__OBJECT
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #13 signal_emit_unlocked_R
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #16 app_create
  • #17 app_clone
  • #18 bonobo_mdi_open_toplevel
  • #19 main
  • #20 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 wait4
    from /lib/i686/libc.so.6 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-12-05 15:32 -------

The original reporter (pvinson@fit.edu) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, maggi@athena.polito.it.
Comment 1 Elijah Newren 2002-12-05 21:32:44 UTC 
Interesting.  Only one other person has reported a problem with a
similar stack trace.  From your description, I'd take a wild guess and
say that a memory leak in another program has eaten up all memory and
prevents gedit from running.  Just a wild guess, though.  Can you try
running gnome-system-monitor when you get the crash to see if this
might be the case?  Also, please add any extra comments to
http://bugzilla.gnome.org/show_bug.cgi?id=95063

Thanks.

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