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 549959 - Open huge files that cannot fit in memory
Open huge files that cannot fit in memory
Status: RESOLVED OBSOLETE
Product: gedit
Classification: Applications
Component: file loading and saving
unspecified
Other All
: Normal enhancement
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2008-08-30 16:25 UTC by Andreas Moog
Modified: 2020-11-24 09:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Andreas Moog 2008-08-30 16:25:53 UTC
Please describe the problem:
mjohansson@bang:~$ ls -la test2.sql
-rw-r--r-- 1 mjohansson mjohansson 2122562112 2008-05-06 10:30 test2.sql

mjohansson@bang:~$ gedit test2.sql
[ ** In the gedit window: ** ]
Could not open the file /home/mjohansson/test2.sql.
Not enough available memory to open the file. Please close some running applications and try again.

It shouldn't try to load the whole document at once if it can't.

Steps to reproduce:
1. Open a file bigger than your amount of physical and swap-memory



Actual results:
The Errormessage appears in gedit-Window.

Expected results:
The file is opened

Does this happen every time?
Yes

Other information:
This bug was filed at Launchpad:
https://bugs.edge.launchpad.net/ubuntu/+source/gedit/+bug/128497
Comment 1 Sébastien Wilmet 2015-04-14 13:09:00 UTC
I confirm, for a general-purpose text editor it can be useful to open really big files.

A workaround is to use command line utilities: grep, sed, etc.
Comment 2 Sébastien Wilmet 2020-11-24 09:59:06 UTC
Mass-closing of all gedit bugzilla tickets.

Special "code" to find again all those gedit bugzilla tickets that were open before the mass-closing:

2bfe1b0590a78457e1f1a6a90fb975f5878cb60064ccfe1d7db76ca0da52f0f3

By searching the above sha256sum in bugzilla, the gedit contributors can find again the tickets. We may be interested to do so when we work on a specific area of the code, to at least know the known problems and possible enhancements.

We do this mass-closing because bugzilla.gnome.org is being replaced by gitlab.gnome.org.