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 462511 - crash in Text Editor: gedit was running in 2 w...
crash in Text Editor: gedit was running in 2 w...
Status: RESOLVED DUPLICATE of bug 352099
Product: gedit
Classification: Applications
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-01 15:51 UTC by rem
Modified: 2007-08-01 16:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description rem 2007-08-01 15:51:56 UTC
Version: 2.18.0

What were you doing when the application crashed?
gedit was running in 2 windows.  In one of the windows was a document that was being created by another program.  I clicked on that document.  It did not display anthing and one cpu went to 100%.  So, I closed gedit.  It said it was not responding;  I said quit.

I restarted gedit.  Loaded 1 document by clicking 2 on the File menu.  Loaded another by clicking 1 on the File menu.  Clicked the Documents menu item to move the 2nd to a new window.  It did that.  Clicked item 4 in the File menu in the new window.  It crashed.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 2195881984 vsize: 2195881984 resident: 24580096 share: 19087360 rss: 24580096 rss_rlim: 4294967295
CPU usage: start_time: 1185983115 rtime: 179 utime: 170 stime: 9 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208178976 (LWP 11003)]
(no debugging symbols found)
0x009c8402 in __kernel_vsyscall ()

Thread 1 (Thread -1208178976 (LWP 11003))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_malloc
    from /lib/libglib-2.0.so.0
  • #10 g_convert_with_iconv
    from /lib/libglib-2.0.so.0
  • #11 g_convert
    from /lib/libglib-2.0.so.0
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
    from /lib/libglib-2.0.so.0
  • #16 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #17 ??
    from /lib/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #19 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 main
  • #0 __kernel_vsyscall

No plugin installed in $HOME.





----------- .xsession-errors ---------------------
--> file:///home/dick
(nautilus:7256): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
** (gnome-system-monitor:7266): WARNING **: SELinux was found but is not enabled.
** (gnome-system-monitor:10655): WARNING **: SELinux was found but is not enabled.
** (gnome-system-monitor:10974): WARNING **: SELinux was found but is not enabled.
GLib-ERROR **: gmem.c:135: failed to allocate 2147483648 bytes
aborting...
--------------------------------------------------
Comment 1 Iestyn Pryce 2007-08-01 16:46:00 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.


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