-
Notifications
You must be signed in to change notification settings - Fork 1
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
NoUnsortedRecords
leads to out-of-memory crash
#15
Comments
Can you please see if you can reproduce this with v1.1.7?
(And run the 1.1.8 example as well just to compare like to like.) |
It's a bit tricky to track down. I can get 1.1.8 to run if I remove the "generated code" folder in .elm-stuff and re-run it on the project. If I try to re-run, It runs out of memory. This is with the '--template' just running this rule. I also experience the same thing with 1.1.7 changing the template version. However, if I install / uninstall the modules with elm-json, I can get 1.1.7 to run pretty consistently, but 1.1.8 crashes. It's kinda like the Anyway, I think I can say that, when running the specific version in my project, 1.1.7 works fine, and 1.1.8 crashes. |
I don't know that this is really "fixable" until elm-review gets type information. As a workaround, you should be able to just increase the heap allocation limit of node. Can you try
or the like (I think the default is only like 1.4 GB or something) and see if that works fine for you? I don't think this is a bug in the rule so much as just running up into the default limits of the node runtime. |
When enabling NoUnsortedRecords in my elm review rules, the process crashes with an out-of-memory error. Disabling this rule allows elm-review to work.
Macbook Pro, M2 Pro, 32GB, macOS Sequoia 15.0 (although it also crashed in previous versions too).
Statistics of project being reviewed:
Stack Trace
The text was updated successfully, but these errors were encountered: