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

Integrating lightningcss-loader causes webpack bus error #671

Open
bagasme opened this issue Feb 5, 2024 · 1 comment
Open

Integrating lightningcss-loader causes webpack bus error #671

bagasme opened this issue Feb 5, 2024 · 1 comment

Comments

@bagasme
Copy link

bagasme commented Feb 5, 2024

Hi,

I'm opening this issue in reference to go-gitea/gitea#29058.

Long story short, I'm trying to build gitea which uses lightningcss-loader 2.1.0. I use node v18.19.0. The build (make) stopped when webpack dumps the core dump due to bus error. Passing NODE_OPTIONS="--max-old-space-size=4096" doesn't seemingly help in this case.

I don't have a time to examine core dumps in depth, so attached below.

@silverwind
Copy link

silverwind commented Feb 5, 2024

If I understand correctly, lightningcss is trying to allocate more memory than the system is willing to provide (4GB total with 4.4GB swap, around 2.4GB usable live memory at time of execution) which the kernel then refuses to allocate and it raises SIGBUS.

Is this enough memory to run it? Are there any minimum memory requirements documented? The source CSS is only around 1-2MB unminified in our case.

Edit: After reading Wikipedia, I think it may not actually be related to available memory size but instead should be a invalid memory address access that the CPU can not address. I think stuff like this should only be possible in unsafe Rust, right?

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

No branches or pull requests

2 participants