-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
Out of heap space crash #196
Comments
I continue to get this as well. <--- Last few GCs ---> [22306:0x450ea20] 658478185 ms: Mark-sweep 988.0 (1000.3) -> 988.0 (1000.3) MB, 1677.1 / 0.0 ms (average mu = 0.444, current mu = 0.102) last resort GC in old space requested <--- JS stacktrace ---> ==== JS stack trace =========================================
Security context: 0x292556dc08d1 FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory |
This seems to be cli-only, the desktop app does not have a memory leak. Is there special library that cabal-cli is using to render things that might need investigation/updating? |
Is anyone running a cli with --seed that is also crashing? If yes, it would clarify whether it's related to rendering.
|
@noffle I looked on my vps, looks like I'm getting
But it is not crashing, it seems to be just a warning. |
A crash report here. I couldn't get all of it because the screen froze. Version is 13.1.6
|
data point: I am not. Both of my instances that are crashing are Linux (Ubuntu and Debian) with just "cabal" as the command. |
i just started a separate process on a vps, seeding the public cabal without the cli rendering. i'll post again in a few days sharing if it crashed |
it crashed during the night |
After roughly a 24-48 hours it will always crash with a javascript out of heap space error (memory leak). This is with one cabal open (the default one) and not much activity.
It's been happening for the last few versions (at least). Fixing this ought to be the top priority, even if it's something in an upstream library.
The text was updated successfully, but these errors were encountered: