GNOME Bugzilla – Bug 95063
gedit crashes when I start it up
Last modified: 2009-08-15 18:40:50 UTC
Package: gedit Severity: normal Version: 2.0.2 Synopsis: gedit crashes when I start it up Bugzilla-Product: gedit Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.0.3) Description: Description of Problem: After some period of time gedit starts to crash when I start it up...it doesn't do after a fresh reboot, though. Steps to reproduce the problem: 1. it just happens..no particular instance. 2. 3. Actual Results: Expected Results: How often does this happen? A LOT Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gedit' (no debugging symbols found)...[New Thread 8192 (LWP 10143)] 0x420ae169 in wait4 () from /lib/i686/libc.so.6
+ Trace 28376
Thread 1 (Thread 8192 (LWP 10143))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-10-07 07:59 ------- 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.
Unique trace
Paolo: is this a gconf bug?
I don't think it is a gconf bug Note that I'm not able to reproduce it.
Apologies for the spam- I'm removing 'bugsquad' from some keywords via the web interface. This is a one-time only thing before I re-add bugsquad via the SQL interface, which will generate no mail. Apologies again.
I'm still not able to reproduce it ... and I use gedit very often :-) Are you still able to reproduce it? Could you please attach a stack trace from a gedit compiled with debugging symbols?
*** Bug 100460 has been marked as a duplicate of this bug. ***
Bug 100460 had some interesting comments that makes it sound like this may be due to a memory leak of some other application that eats up all available memory. Of course, this is just a guess on my part. But it seems to be backed up by the fact that the reporter of this bug says that it never happens after a fresh reboot. Here's the relevant comments from 100460: 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 Also, there was one other comment in 100460 that might be relevant, but it doesn't really affect the memory leak theory either way: 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. Because of this other bug report, I'm going to reopen.
James (aka snorp): could you please give a look at this bug?
Is someone still having this problem?
Closing it since nobody seems to be able to reproduce it.
*** Bug 116504 has been marked as a duplicate of this bug. ***
*** Bug 116622 has been marked as a duplicate of this bug. ***
*** Bug 122241 has been marked as a duplicate of this bug. ***
Please, note that all the duplicates of this bug are related to gedit 2.0.2. I have not seen duplicates related to a newer version of gedit so I suppose that somehow this bug has been fixed. If you see this same bug reported against a newer version of gedit (2.x.x with x >= 2), please, reopen it.