Bug 356734 – crash in Text Editor: opening a 800 meg text f...

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 356734 - crash in Text Editor: opening a 800 meg text f...


Summary:	crash in Text Editor: opening a 800 meg text f...


Status:	RESOLVED DUPLICATE of bug 352099

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-09-19 13:35 UTC by blizzard_hwc
Modified:	2006-09-20 07:57 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description blizzard_hwc 2006-09-19 13:35:56 UTC

Version: 2.16.0

What were you doing when the application crashed?
opening a 800 meg text file


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 1882259456 vsize: 0 resident: 1882259456 share: 0 rss: 1425616896 rss_rlim: 0
CPU usage: start_time: 1158672786 rtime: 0 utime: 1015 stime: 0 cutime:894 cstime: 0 timeout: 121 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208866416 (LWP 4116)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 72743

Thread 1 (Thread -1208866416 (LWP 4116))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 *__GI_raise
from /lib/tls/i686/cmov/libc.so.6
#6 *__GI_abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_realloc
from /usr/lib/libglib-2.0.so.0
#10 g_convert_with_iconv
from /usr/lib/libglib-2.0.so.0
#11 g_convert
from /usr/lib/libglib-2.0.so.0
#12 gedit_convert_from_utf8
#13 gedit_convert_to_utf8
#14 gedit_document_new
#15 gedit_document_new
#16 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#17 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#18 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#19 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#20 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#21 main
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-09-19 14:47:30 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.

Also, the maintainers need more information to fix the bug. Could you please answer the questions in the other report?


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

Comment 2 Paolo Maggi 2006-09-20 07:57:29 UTC

The crash is due to an out-of-memory condition.
I'm not sure how we should manage these cases, we should probably try to "convert to UTF-8" in an incremental way.