Bug 384314 – crash in Text Editor: ouverture d'un gros fich...

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 384314 - crash in Text Editor: ouverture d'un gros fich...


Summary:	crash in Text Editor: ouverture d'un gros fich...


Status:	RESOLVED DUPLICATE of bug 352099

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-10 10:48 UTC by cedric
Modified:	2006-12-10 10:50 UTC

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

Description cedric 2006-12-10 10:48:04 UTC

Version: 2.15.9

What were you doing when the application crashed?
ouverture d'un gros fichier (environ 1 Gb) de type sql dump	


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled
----------- .xsession-errors ---------------------
** (Terminal:8167): WARNING **: Aucune manipulation définie pour la séquence de contrôle « device-control-string ».
** (Terminal:8167): WARNING **: Aucune manipulation définie pour la séquence de contrôle « device-control-string ».
** (Terminal:8167): WARNING **: Aucune manipulation définie pour la séquence de contrôle « device-control-string ».
Error: No running window found
Error: No running window found
Error: No running window found
Error: No running window found
GLib-ERROR **: gmem.c:135: failed to allocate 998535286 bytes
aborting...
** (bug-buddy:32536): WARNING **: Impossible de charger l'icône pour Ouvrir le dossier
--------------------------------------------------

Memory status: size: 1064755200 vsize: 0 resident: 1064755200 share: 0 rss: 592203776 rss_rlim: 0
CPU usage: start_time: 1165747560 rtime: 0 utime: 601 stime: 0 cutime:479 cstime: 0 timeout: 122 it_real_value: 0 frequency: 0

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 -1208195376 (LWP 32533)]
(no debugging symbols found)
0x00ee6402 in __kernel_vsyscall ()

+ Trace 92994

Thread 1 (Thread -1208195376 (LWP 32533))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/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/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 gedit_convert_from_utf8
#13 gedit_convert_to_utf8
#14 gedit_document_new
#15 gedit_document_new
#16 g_source_get_current_time
from /lib/libglib-2.0.so.0
#17 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#18 g_main_context_check
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

Comment 1 Damien Durand 2006-12-10 10:50:22 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 ***