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 357459 - Meld performs really bad while typing
Meld performs really bad while typing
Status: VERIFIED DUPLICATE of bug 168139
Product: meld
Classification: Other
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Stephen Kennedy
Stephen Kennedy
Depends on:
Blocks:
 
 
Reported: 2006-09-24 14:28 UTC by Sven Herzberg
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sven Herzberg 2006-09-24 14:28:30 UTC 
I'm using the full-blown meld (with line numbers and syntax highlighting) on two files with approx. 2500 lines. When I'm typing, meld increases its CPU load to almost 100% and comes back quite late.

Proposal:
Add a marker for a "dirty region" which needs to be rechecked. If the user types, save the timestamp, mark this area as dirty and add a g_timeout to perform the update.
This timeout could wake up all 0.5 seconds and check whether the user has typed during the past 0.5 seconds: If he typed, do nothing. If he didn't, perform the update.
Comment 1 Stephen Kennedy 2006-09-24 18:26:11 UTC 
Yes, meld can be slow with large files. I've previously tried the "wait for idle" approach but the details are tricky (I invite you to try!)

Meld already reruns the diff only on the part which has changed. Part of the problem is that the difflib algorithm is not amenable to partial changes. Part of the problem is that the difflib algorithm can be really, really slow.
Comment 2 Stephen Kennedy 2006-10-21 11:29:50 UTC 

*** This bug has been marked as a duplicate of 168139 ***
Comment 3 Stephen Kennedy 2006-11-19 11:06:06 UTC 
Batch close of old bugs.