Skip to content
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

Version 7.0.1/8.0.0 can cause memory problems on Windows #192

Open
harmboschloo opened this issue Aug 27, 2020 · 1 comment · May be fixed by #228
Open

Version 7.0.1/8.0.0 can cause memory problems on Windows #192

harmboschloo opened this issue Aug 27, 2020 · 1 comment · May be fixed by #228

Comments

@harmboschloo
Copy link

I'm trying to upgrade elm-webpack-loader from 6.0.1 to 7.0.1.

But during compilation I get a bunch of lines like this (sorry it's in Dutch):

elm.exe: getMBlocks: VirtualAlloc MEM_COMMIT failed: Het wisselbestand is te klein voor het voltooien van deze bewerking.

It says the virtual memory is too small to complete the operation. I'm compiling 28 elm entry points files.

I increased my virtual memory which made the problem go away. But that doesn't seem like a desired solution for this problem.

I saw that the maxInstances option was removed in d4ec59a#diff-168726dbe96b3ce427e7fedce31bb0bcL157. So now all elm entry points are compiled in parallel. Maybe it's a good idea to revert that change and and prevent these kind of problems.

@harmboschloo
Copy link
Author

I increased my virtual memory which made the problem go away.

That didn't work when I tried to compile a project with about 50 elm entry points, and VSCode crashed 😅

@harmboschloo harmboschloo changed the title Version 7.0.1 can cause memory problems on Windows 10 Version 7.0.1/8.0.0 can cause memory problems on Windows 10 Aug 25, 2022
@harmboschloo harmboschloo changed the title Version 7.0.1/8.0.0 can cause memory problems on Windows 10 Version 7.0.1/8.0.0 can cause memory problems on Windows Aug 25, 2022
@harmboschloo harmboschloo linked a pull request Sep 7, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant