Bug 378226 – crash in Text Editor: Abrir un archivo de text...

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 378226 - crash in Text Editor: Abrir un archivo de text...


Summary:	crash in Text Editor: Abrir un archivo de text...


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-11-22 19:55 UTC by masao
Modified:	2006-11-22 21:13 UTC

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

Description masao 2006-11-22 19:55:56 UTC

Version: 2.16.1

What were you doing when the application crashed?
Abrir un archivo de texto de 235 mbytes.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 318197760 vsize: 0 resident: 318197760 share: 0 rss: 139681792 rss_rlim: 0
CPU usage: start_time: 1164225223 rtime: 0 utime: 240 stime: 0 cutime:192 cstime: 0 timeout: 48 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 -1226787152 (LWP 8913)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 88581

Thread 1 (Thread -1226787152 (LWP 8913))

#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 raise
from /lib/tls/i686/cmov/libc.so.6
#6 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_malloc
from /usr/lib/libglib-2.0.so.0
#10 g_strndup
from /usr/lib/libglib-2.0.so.0
#11 gedit_convert_from_utf8
#12 gedit_convert_to_utf8
#13 gedit_document_new
#14 gedit_document_new
#15 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#16 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#17 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#18 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#19 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#20 main
#0 __kernel_vsyscall

Comment 1 Damien Durand 2006-11-22 21:13:19 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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