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 743415 - gedit is much slower than less for reading the same file
gedit is much slower than less for reading the same file
Status: RESOLVED DUPLICATE of bug 172099
Product: gedit
Classification: Applications
Component: general
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2015-01-23 17:23 UTC by Pacho Ramos
Modified: 2015-01-23 18:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
build.log.xz (193.84 KB, application/octet-stream)
2015-01-23 17:23 UTC, Pacho Ramos
Details

Description Pacho Ramos 2015-01-23 17:23:35 UTC
Created attachment 295294 [details]
build.log.xz

Personally I try to avoid gedit usage for reading files because it's really much slower than less for doing the same tasks and also eats a lot of resources.

Try to read the attached file as-is (even keeping it compressed)
1. First scenario:
$ less build.log.xz -> it's instant for me, then, I simply press "/mktm" to search that string and it reports me instantly that it doesn't exist

2. Second scenarion:
- Click on the file, it's opened by file-roller and I click on the file, file-rollers choosed gedit to open it and... it takes multiple seconds to load full file. Once it's loaded, it also takes time to search the same string

Thanks for your help. I am running 3.14 but I have always seen this then, it's not a regression I think
Comment 1 Sébastien Wilmet 2015-01-23 18:09:14 UTC

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