-
Notifications
You must be signed in to change notification settings - Fork 30.7k
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
Node 22 on armvc6 and armv7 get into an out of memory infinite loop #53489
Comments
@isheludko, could you take a look? I think this is related to CodeRange allocation logic which seems in your wheelhouse. I tried this on my computer and I don't think it's actually running out of memory like the above message suggests at first glance. It starts counting down and then eventually the memory pointer loops around to negative then underflows to positive again, looping forever:
BUT on AMD64, I also see the same error many times. But it eventually stops when
|
Unfortunately, I'm not allowed to run docker on my machine. Is there another way of reproducing the issue on x64 Linux? Maybe using qemu? BTW, IIUC a standalone V8 build (d8 binary) should suffer from the same issue... Do you mind filing a bug in Chromium bug tracker with instructions not involving docker? |
I figured it was CodeRange related because I'm not sure how I'd produce this without docker. Can you use Here's the full output of: |
Ok, I reproduced the issue with
where
All I'm getting from GDB is this:
BTW, I still don't see how |
Okay. I'm getting the same, and a little googling tells me gdb doesn't work under qemu (though I don't really know how to use either tool well).
Good call. It's not unlikely I misread the code and accidentally thought code in It very well could be in d8.cc inside I still get the same problem with |
I'll keep on trying to move forward with this issue but with a lower priority. |
It is important, I can not package node 19+ into alpine(docker), I will get into an out of memory infinite loop.(armvc6 and armv7,s390x,etc ) |
Noodled around with this some more. I have found additionally that:
|
This doesn't seem to loop forever on my Windows x64 PC. It does perform lots of The end of the equivalent loop on arm looks like:
The end of the equivalent but much shorter loop on aarch64 looks like:
Full log output: |
I tried installing Alpine linux to Arm32/Aarch64 qemu machines in a hope that I'll be able to run gdb there but node worked just fine. Honestly, I'm out of ideas about how to proceed with this issue without being able to run a debugger. |
Today this does seem to loop forever on my Windows x64 PC, and the |
Version
22
Platform
Linux 431b32e3d8c4 6.6.31-linuxkit #1 SMP Thu May 23 08:36:57 UTC 2024 armv7l Linux
Subsystem
No response
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
Every time
What is the expected behavior? Why is that the expected behavior?
Container starts
What do you see instead?
Without trace, the container just hangs, with tracing the following log is output forever
Additional information
No response
The text was updated successfully, but these errors were encountered: