-
Notifications
You must be signed in to change notification settings - Fork 18
Editor freezes when using atom-blame in large files #31
Comments
I've been able to reproduce this as well. I see it in files with a similar number of lines and number of commits. I wonder if whatever's being done could be done either off the main thread or done incrementally (perhaps with a progress indicator). If some lines' blame info has been displayed, and other lines' blame info is still being gathered or rendered, it may be good to color those lines differently in the gutter so the user knows the blame info is pending, and isn't led to believe a line that hasn't been picked up yet is simply part of the same commit as the most recently rendered line of blame info. This could easily be done by using the 10px or so of color applied on the left side of the gutter. For lines that are pending, the color could be diagonal striped, similar to bootstrap's progress bars. |
Could you try if the |
Ok I tried out the |
@MoritzKn Do you have an open source project where I can reproduce that? |
@josa42 As I said, I could reproduce this in the atom editor git repository with the file |
Oops 🙃. Thanks |
Any news about this? I'm experiencing the same issue. |
This issue still exists. |
The same problem |
+1 Large json + 4k lines - freeze and crash |
When using atom-blame on large files (1500+ lines) in a git repository with a long history (2500+ commits) my Editor freezes and I have to kill the process. In smaller files it sometimes takes one or two seconds to load the blame.
I am using 1.13.0 and atom-blame 0.10.2 on GNU/Linux.
Let me know if you need more information.
The text was updated successfully, but these errors were encountered: