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 756400 - Gedit becomes non-responsive when moving the caret into very long line with syntax highlighting enabled
Gedit becomes non-responsive when moving the caret into very long line with s...
Status: RESOLVED DUPLICATE of bug 127731
Product: gedit
Classification: Applications
Component: general
3.18.x
Other Linux
: Normal major
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2015-10-11 19:19 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2015-10-15 14:12 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
test case (53.85 KB, text/css)
2015-10-11 19:19 UTC, Joanmarie Diggs (IRC: joanie) 		Details

Description Joanmarie Diggs (IRC: joanie) 2015-10-11 19:19:18 UTC 
Created attachment 313073 [details]
test case

Steps to reproduce:
1. Open the attached document (browser-saved css file from gnome.org) in Gedit
2. Click/arrow to move the caret amongst the characters in first three lines
3. Click/arrow to move the caret to the fourth line
4. Get into the app menu and choose Preferences.

Expected results: Gedit would not become non-responsive.

Actual results: Gedit becomes non-responsive for a prolonged period of time. GNOME displays a dialog asking if you want to force quit Gedit or wait.
Comment 1 Sébastien Wilmet 2015-10-15 12:24:32 UTC 
Yet another duplicate.

*** This bug has been marked as a duplicate of bug 127731 ***
Comment 2 Joanmarie Diggs (IRC: joanie) 2015-10-15 13:10:26 UTC 
(In reply to Sébastien Wilmet from comment #1)
> Yet another duplicate.
> 
> *** This bug has been marked as a duplicate of bug 127731 ***

My bad. I thought it was different because if syntax highlighting is disabled, there's no non-responsiveness. Even though the "line" is huge.
Comment 3 Sébastien Wilmet 2015-10-15 14:12:14 UTC 
The problem apparently occurs when there are lots of tags applied, e.g. with syntax highlighting, when highlighting search occurrences, etc.