Bug 478391 – crash in Text Editor: Editting the maillog fil...

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 478391 - crash in Text Editor: Editting the maillog fil...


Summary:	crash in Text Editor: Editting the maillog fil...


Status:	RESOLVED DUPLICATE of bug 352099

Product:	gedit
Classification:	Applications
Component:	general
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Gedit maintainers
QA Contact:	Gedit maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-09-19 19:45 UTC by keith
Modified:	2007-09-21 19:31 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description keith 2007-09-19 19:45:22 UTC

Version: 2.18.2

What were you doing when the application crashed?
Editting the maillog file (around 1.5Gb)


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.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 1557786624 vsize: 1557786624 resident: 401186816 share: 400601088 rss: 401186816 rss_rlim: 4294967295
CPU usage: start_time: 1190230847 rtime: 943 utime: 671 stime: 272 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 -1208191264 (LWP 11249)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 164012

Thread 1 (Thread -1208191264 (LWP 11249))

#0 __kernel_vsyscall
#1 waitpid
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_strndup
from /lib/libglib-2.0.so.0
#11 ??
#12 gedit_convert_to_utf8
#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.

Module versions:
  - glib                  
  - 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 (19 sec old) ---------------------
localuser:root being added to access control list
SESSION_MANAGER=local/mars.on-time.co.uk:/tmp/.ICE-unix/11000
Unable to open desktop file /usr/share/applications/openoffice.org-1.9-writer.desktop for panel launcher: No such file or directory
Unable to open desktop file /usr/share/applications/openoffice.org-1.9-impress.desktop for panel launcher: No such file or directory
Unable to open desktop file /usr/share/applications/openoffice.org-1.9-calc.desktop for panel launcher: No such file or directory
GLib-ERROR **: gmem.c:135: failed to allocate 1484065111 bytes
aborting...
--------------------------------------------------

Comment 1 Paolo Borelli 2007-09-21 19:31:01 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 ***