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 670064 - Load file contents lazily when scrolling
Load file contents lazily when scrolling
Status: RESOLVED WONTFIX
Product: gtksourceview
Classification: Platform
Component: File loading and saving
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: GTK Sourceview maintainers
GTK Sourceview maintainers
Depends on:
Blocks:
 
 
Reported: 2012-02-14 12:54 UTC by Vadim Rutkovsky
Modified: 2016-06-12 11:07 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Vadim Rutkovsky 2012-02-14 12:54:25 UTC 
Original Report: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/911772

I have opended a kernel.log which has so much entries that gedit was not able to reach then end of the document.

On closing this fiel gedit SIGSEV was catched by apport deamon.

I would like to attach the kernel log for reproducing purposes, but it has a size of 1.6GB, so attaching seems not to be indicated.

Stacktrace:
 #0 info_bar_set_progress (tab=<optimized out>, size=6, total_size=1) at gedit-tab.c:894
         __PRETTY_FUNCTION__ = "info_bar_set_progress"
 Cannot access memory at address 0x7fffd1e5b458
StacktraceTop: info_bar_set_progress (tab=<optimized out>, size=6, total_size=1) at gedit-tab.c:894
Comment 1 Sébastien Wilmet 2013-11-09 19:42:45 UTC 
It is known that very big files can not be opened with gedit. Ideally, the file contents should be loaded lazily. Only when we scroll, the contents is loaded. If too much memory is used, free some of the contents.
Comment 2 Sébastien Wilmet 2016-06-12 11:07:02 UTC 
But GtkTextView was not really meant to be used like that. I think it will never be fixed as long as GtkTextView is used. It is not worth keeping this bug open in bugzilla forever.