-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[wasm] v8 crashing at the end with "Reached heap limit" - for AOT builds #88497
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsRolling build, and log:
Another instance - build, and log. This was hit twice in three rolling build runs. Changes from the last passing build before the first hit: 76a8f4f...18321c6 . cc @vargaz
|
Can't reproduce with the same seed. Tried setting --max-heap-size= as well, it crashes with 512, but works with 612, so the app uses about 600mb of heap. |
Did we disable this test or did it stop happening? |
This might be the same as: |
I think these run close to the limit, and sometimes end up exceeding the heap limit, so we don't see them all the time. |
System.Collections.Immutable.Tests
- v8 crashing at the end with "Reached heap limit" - for AOT builds
right but @kg fixed an issue that may have resolved this |
Does this still happen after that fix ? |
I have not seen this recently. |
Closing this. It can be re-opened if it is hit again. |
Rolling build, and log:
Another instance - build, and log.
This was hit twice in three rolling build runs. Changes from the last passing build before the first hit: 76a8f4f...18321c6 .
cc @vargaz
Known Issue Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=331212
Error message validated:
Fatal JavaScript out of memory: Reached heap limit
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/6/2023 10:39:28 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: