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 479077 - crash in Text Editor: Trying to open a very la...
crash in Text Editor: Trying to open a very la...
Status: RESOLVED DUPLICATE of bug 352099
Product: gedit
Classification: Applications
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-21 19:51 UTC by joseph.yaroch
Modified: 2007-09-23 07:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Attachments
output from gdb (4.18 KB, text/plain)
2007-09-23 04:49 UTC, joseph.yaroch
Details

Description joseph.yaroch 2007-09-21 19:51:45 UTC
Version: 2.18.1

What were you doing when the application crashed?
Trying to open a very large CSV  file (~1.7GB)


Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.18.3 2007-09-18 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-sabayon #1 Wed Sep 19 04:30:24 MDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Human-Graphite
Icon Theme: Tango

Memory status: size: 1928667136 vsize: 1928667136 resident: 682065920 share: 681463808 rss: 682065920 rss_rlim: 4294967295
CPU usage: start_time: 1190400341 rtime: 1651 utime: 1337 stime: 314 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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)
0xb79ada6e in waitpid () from /lib/libpthread.so.0
  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 ??
  • #3 ??
  • #4 ??

No plugin installed in $HOME.

Module versions:
  - glib                  2.12.13
  - gtk+                  2.10.14
  - gtksourceview         1.8.5
  - libgnomeui            2.18.1
  - libglade              2.6.1
  - libgnomeprintui       2.18.0
  - gnome-vfs             2.18.1
  - pygobject             2.12.3
  - pygtk                 2.10.6
  - gnome-python          2.18.2
  - gnome-python-desktop  2.18.0
  - enchant               1.2.5
  - iso-codes             0.58

Python module versions:
  - python                2.5.1
  - pygtk                 2.10.6 (GTK+ 2.10.14)
  - gnome-python          2.18.2





----------- .xsession-errors (24 sec old) ---------------------
kio (KIOConnection): ERROR: Could not write data
kio (KIOConnection): ERROR: Could not write data
kio (KIOConnection): ERROR: Could not write data
kio (KMimeType): WARNING: mimetype not valid '' (missing entry in the file ?)
kio (KMimeType): WARNING: mimetype not valid '' (missing entry in the file ?)
kparts: WARNING: StatusBarExtension::removeStatusBarItem. Widget not found : [KPushButton pointer (0x81cfbc8) to widget CancelButton, geometry=100x30+0+0]
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x3e00073
KFileMetaInfo: WARNING: KTxtPlugin was created for text/x-csv but doesn't call addMimeTypeInfo for it!
KFileMetaInfo: WARNING: KTxtPlugin was created for text/x-csv but doesn't call addMimeTypeInfo for it!
GLib-ERROR **: gmem.c:135: failed to allocate 1813420676 bytes
aborting...
--------------------------------------------------
Comment 1 Paolo Borelli 2007-09-22 10:05:37 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 joseph.yaroch 2007-09-23 04:49:05 UTC
Created attachment 96043 [details]
output from gdb
Comment 3 joseph.yaroch 2007-09-23 04:50:08 UTC
(In reply to comment #1)
> Thanks for taking the time to report this bug.
> Without a stack trace from the crash it's very hard to determine what caused
> it.
> Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces
> for more information on how to do so. Thanks in advance!
> 

This is the stack trace (attached).  I hope it has the information you need. If you need the data file to try to reproduce the error, it is located at http://nppesdata.cms.hhs.gov/cms_NPI_files.html.

Comment 4 Paolo Borelli 2007-09-23 07:28:44 UTC
thanks for following up. The stack trace is still incomplete (it lacks symbols), but it is enough for me to see that the problem is due to the fact that you ran out of memory. This is  a duplicate of bug 352099.

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