Composer error with The windows terminated unexpectedly (reason: ‘oom’,code:‘-536870904’) , running on windows 10 , 16 GB Memory
2 Likes
As it says it ran out of memory (OOM). Likely you need to open the Process Explorer. Following thread has several options to analyze that.
After trying some methods found online, I discovered that the problem was related to the chat context. Moreover, I couldn’t directly locate and delete the context file corresponding to this project within Cursor. So, I copied the project’s source code, opened a new window, and reopened the project. The problem was perfectly resolved. Therefore, it is recommended not to have too much context, as this issue may occur in the Windows environment.
1 Like
Hello, ‘oom code’, make me crazy. I see I’m not the only one : 0.46.9, vscode 1.96.2
i have to manually remove all the storage & caches manually to make it work. It used to crash like every minute for me, and using over 10G memory. After deleting those files, it uses only 700M memory. Can you just add a feature to reset the context window?
helleo!
Can you explain in detail how you did this, I’m having the same problem.
Save the context of your chat in the README file, and copy your project files. Open a new Cursor window and then open the newly created project folder, and this should solve the problem.
This isn’t an issue with the Cursor, context windows or with people actually running out of memory. The issue is with the Visual Studio Code version that they’re using - which is a known problem with this version.
The team at Cursor should fix this issue though with their modified VSC version since the crash will use up multiple requests since they need to be resent.
Hey thanks for the hint.
How exactly can I do that?
the brutal way is to open the cache director (%APPDATA%\Cursor), and remove everything. This has no impact to your code, but will remove all caches and memory, and settings of cursor.
I always hit the no memory crash if I have many changes not accepted, or used the same chat window too long, or tried to restore from an older version. Almost 100% reproducible…
My computer cpu and ram(32g) is not used up but still constantly hit this (reason: ‘oom’,code:’-536870904’) problem. What should I do team?
Performance and crashes should be improved in 0.48.x, which is available under Cursor Settings > Beta > Update Frequency: Early Access
Please try it and let us know your experience
Hey, please check this: