Painfully slow buffer-update for large files about text-buffer HOT 5 CLOSED

@ArekSredzki Just to make sure: are these files located in a Git repository? If so, do the performance problems still happen if you move them into a non-Git repository?

from text-buffer.

@50Wliu The files are in a Git repository, however I just performed a test outside of any repos and the result was the same. The file I did it with was a bit bigger and the IDE is still blocked ten minutes later.

Looking through jsdiff's release notes, it sounds like this and many other issues have been resolved. I was about to submit a PR to rebase atom/jsdiff but I think the best action is to abolish it all together & just use the main branch kpdecker/jsdiff seeing as there is active development going on there, and absolutely none on the atom fork. Your thoughts?

from text-buffer.

@ArekSredzki That sounds great, especially if the line endings issue documented in @benogle's fork was fixed.

EDIT: Actually it seems like it has...no idea why we're using a horribly outdated fork then 😕.

from text-buffer.

@50Wliu Great! I'm so happy to hear that my troubles with this will soon be over! His commit seems to have been pulled into the main repo soon after the atom fork was made, so it's been fixed just the same there 👍 Any ideas as to when these changes would make it into the atom release?

from text-buffer.

@ArekSredzki It depends on when we switch to the main repo. If we're lucky it'll be out in Atom 1.7.0, if not Atom 1.8.0 or beyond. I'll go create a PR.

from text-buffer.