-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automatically Opens Previous Session of a File That's Too Large to Process #336
Comments
The application state, such as opened documents is for me saved in But generally opening large files should not have this effect. Someone should look into that. So thanks a lot for letting us know! |
Cleared that directory and was able to open XiEditor without problems! |
Definitely something weird going on there. I have no problems opening my ~1GB concatenated IRC log file. Takes a while but doesn't use any meaningful amount of CPU. One problem I can think of is if your file has long lines and you have word wrap enabled - word wrap is kinda useless at the moment. Does that happen to be the case by chance? |
word wrap is actually working reasonably well at the moment, although performance still isn't quite where we'd want it to be. Files with no newlines are likely still a problem, though. |
It does have excessively long individual lines. Each line has about 17,500 characters. It's a series of inserts to a database with 731 columns (don't ask). How do you disable word wrap? I could see if that helps. |
Found it in the settings. I already had it disabled, so that's not the issue.
|
Yea, this sounds like #20. |
I opened a file in XiEditor that turned out to be too large to process (31.5 MB). The editor started using all of my CPU and making my macbook overheat, so I went into the activity monitor and force killed the process. Now whenever I open XiEditor it has that previous session cached and attempts to open the large file again, thus causing it to crash and forcing me to kill the process again. Is there a way to change the settings to not restore from a previous session by default? Or perhaps a way to clear out the cache of the software so it doesn't have that previous session information anymore? I tried uninstalling and re-cloning to no avail, it seems the session information is stored somewhere outside of the repo itself.
The text was updated successfully, but these errors were encountered: