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 391175 - crash in Text Editor: Loading a really large (...
crash in Text Editor: Loading a really large (...
Status: RESOLVED DUPLICATE of bug 352099
Product: gedit
Classification: Applications
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2006-12-31 02:50 UTC by strager.nds
Modified: 2006-12-31 15:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16

Attachments
Detailed crash information. (6.92 KB, text/plain)
2006-12-31 14:36 UTC, strager.nds 		Details

Description strager.nds 2006-12-31 02:50:13 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Loading a really large (1.6GB?) text file.


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

Memory status: size: 1671168 vsize: 0 resident: 1671168 share: 0 rss: 200704 rss_rlim: 0
CPU usage: start_time: 1167490822 rtime: 0 utime: 105 stime: 0 cutime:0 cstime: 0 timeout: 105 it_real_value: 0 frequency: 110923

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
Comment 1 Susana 2006-12-31 03:34:40 UTC 
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 strager.nds 2006-12-31 14:36:45 UTC 
Created attachment 79096 [details]
Detailed crash information.

Recreated the crash using the same file, in the same manner.

I opened gedit with the filename as a parameter.  (I did not open gedit and then open the file using the file-open dialog.)
Comment 3 Paolo Maggi 2006-12-31 15:41:10 UTC 
Thanks for taking the time to reproduce this bug and reporting as more details.

This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

Note that gedit has problems managing very big files. We will try to solve this problem in the future.


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