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 477525 - crash in Text Editor: Loading a very very very...
crash in Text Editor: Loading a very very very...
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-09-16 16:20 UTC by baileyz
Modified: 2007-12-25 12:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description baileyz 2007-09-16 16:20:02 UTC
Version: 2.18.2

What were you doing when the application crashed?
Loading a very very very large file to check content if it is at it should


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2931.fc7xen #1 SMP Mon Aug 13 10:12:37 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 1508597760 vsize: 1508597760 resident: 1242214400 share: 504684544 rss: 1242214400 rss_rlim: 4294967295
CPU usage: start_time: 1189959477 rtime: 1132 utime: 778 stime: 354 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208764176 (LWP 31296)]
(no debugging symbols found)
0x00808402 in __kernel_vsyscall ()

Thread 1 (Thread -1208764176 (LWP 31296))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/i686/nosegneg/libc.so.6
  • #6 abort
    from /lib/i686/nosegneg/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_realloc
    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 gedit_convert_to_utf8
  • #14 ??
  • #15 ??
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #18 ??
    from /lib/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #20 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 main
  • #0 __kernel_vsyscall

No plugin installed in $HOME.

Module versions:
  - glib                  2.12.13
  - gtk+                  
  - gtksourceview         
  - libgnomeui            
  - libglade              
  - libgnomeprintui       
  - gnome-vfs             
  - pygobject             
  - pygtk                 
  - gnome-python          
  - gnome-python-desktop  2.18.0
  - enchant               
  - iso-codes             

Python module versions:
  - python                2.5
  - pygtk                 2.10.6 (GTK+ 2.10.14)
  - gnome-python          2.18.1





----------- .xsession-errors (11 sec old) ---------------------
Playing /home/pascal/Download/torrents-fini/Resident.Evil.Extinction(2007)DvDrip/Resident.Evil.Extinction(2007)DvDrip.avi.
Exiting... (Exit)
VLC media player 0.8.6c Janus
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2600090 (VLC media )
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
[00000313] main playlist: nothing to play
[00000313] main playlist: stopping playback
kbuildsycoca running...
Reusing existing ksycoca
GLib-ERROR **: gmem.c:172: failed to allocate 1468006402 bytes
aborting...
--------------------------------------------------
Comment 1 rhb 2007-09-29 22:03:54 UTC
Apparently holding 1.5 gb memory and asking for 1.4 gb more and may have run out of virtual memory limit.  Avi file is likely to be multi-MB binary file, very unfriendly for a text editor.

I have experienced a case of extreme memory usage in gedit that may be related.  In my case, it was a 3 mb file, all alphabetic with no whitespace or punctuation.  My machine thrashed until I killed the task manually.  I saw high cpu usage some of the time, plus wildly varying memory usage.  I know I saw it go over 90 mb, and I thought I saw over 300 mb used, yet it dropped back to as low as 12 mb afterward.

I would guess it's either trying to figure out the file type or trying to split lines for display.  I could get a crash if there is a way to run it in a sandbox with a limit on allowable memory.  In fact, I'd love to impose a 'modest' memory limit on all tasks by default, to derail runaway trains early.

I'm running ubuntu 6.06 with gedit 2.14.4.
Comment 2 Teppo Turtiainen 2007-12-25 12:42:49 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 ***