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 400062 - crash in Text Editor: Loading a very large (50...
crash in Text Editor: Loading a very large (50...
Status: RESOLVED DUPLICATE of bug 352099
Product: gedit
Classification: Applications
Component: general
2.15.x
Other All
: High critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-24 02:59 UTC by farrendoug
Modified: 2007-01-24 11:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description farrendoug 2007-01-24 02:59:19 UTC
Version: 2.15.9

What were you doing when the application crashed?
Loading a very large (500+Meg) text file


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.2869.fc6 #1 SMP Wed Dec 20 14:51:46 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled
----------- .xsession-errors (588576 sec old) ---------------------
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
...Too much output, ignoring rest...
--------------------------------------------------

Memory status: size: 1209151488 vsize: 0 resident: 1209151488 share: 0 rss: 284667904 rss_rlim: 0
CPU usage: start_time: 1169606975 rtime: 0 utime: 1008 stime: 0 cutime:703 cstime: 0 timeout: 305 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 -1208157632 (LWP 4164)]
(no debugging symbols found)
0x00994402 in __kernel_vsyscall ()

Thread 1 (Thread -1208157632 (LWP 4164))

  • #0 __kernel_vsyscall
  • #1 waitpid
    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_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 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 2007-01-24 11:46:47 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 ***