gedit crashes when manipulating 2.8GB text file

[rusivi2]

Binary package hint: gedit

1) lsb_release -rd
Description: Ubuntu 10.04.1 LTS
Release: 10.04

2) apt-cache policy gedit
gedit:
  Installed: 2.30.3-0ubuntu0.1
  Candidate: 2.30.3-0ubuntu0.1
  Version table:
 *** 2.30.3-0ubuntu0.1 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
        100 /var/lib/dpkg/status
     2.30.0git20100413-0ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages

3) What I expected to happen is that when I open up a 2.8GB text file with gedit, it will allow me to migrate around the file without crashing.

4) What happened instead is that the file initially opens successfully. However, each of three times it gets about 1/2 the way through loading, the window just closes without my having closed it.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gedit 2.30.3-0ubuntu0.1
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
Date: Thu Aug 19 18:47:57 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: gedit

[Vallery Lancey (muscovy)]

For more details, try running gedit from a terminal and pasting the errors. Thanks for reporting this bug.

[rusivi2 (rusivi2-deactivatedaccount)]

name@name-laptop:~/Desktop/id$ gedit CLI-output.txt

GLib-ERROR **: (NULL) message
aborting...
Aborted

[Pedro Villavicencio (pedro)]

Thanks for sent it upstream.

[Pedro Villavicencio (pedro)]

comment from upstream

"It would not be possible to open a 2.8GB file in a 32 bits system, whatever the
application is, if it reads it completely as gedit does.

The reason for that is simple: on a 32bits architecture, a process can only map
3 GB of memory. If you consider 2.8GB of content, with all the required
bookkeeping information (like the btree used for storing the files lines), the
libraries and so on would be much over the 3GB limit.

Hence the error message here:
    0x89689c "%s: failed to allocate %u bytes", args1=0xbfffeb0c "pi\211")

Which itself cannot be displayed (the "NULL" you see) because the final message
cannot be allocated...

I suggest either you split your file or you use another adapted text reader
(which won't need to allocate the entirety of the file, as opposed to a
full-fledged editor) to read it properly..."

[rusivi2 (rusivi2-deactivatedaccount)]

 I did use Vi to manipulate the file, which itself creates a full, temporary copy of the file while the file is being edited. However, it would be nice if gedit had some provision to deal with "large" files.