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

v1.73 miner FATAL ERROR: Committing semi space failed. Allocation failed - JavaScript heap out of memory #3763

Open
crProductGuy opened this issue Apr 7, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@crProductGuy
Copy link
Contributor

What happened?

Ran official pool mining for several days with 16 threads on an 8-core Ryzen, my typical setup on Windows.

Found miner stopped with the error.
Had not seen anything like this error when mining since probably summer 2022

Machine has 32GB RAM and wasn't doing anything else significant, so it wasn't machine resources that caused the OOM error
mining on same code for 6 hours.
Mining now for several hours shows RAM usage 6.8GB in use.

Version

0.1.73

Debug output

Iron Fish version               0.1.73 @ dd7bcab
Iron Fish library               0.0.50 @ dd7bcab
Operating system                Windows_NT x64
CPU model(s)                    AMD Ryzen 7 5700G with Radeon Graphics
CPU threads                     16
RAM total                       31.34 GiB
Heap total                      3.99 GiB
Node version                    v18.13.0
ironfish in PATH                true
Garbage Collector Exposed       false
Telemetry enabled               true
Node name                       ProductGuy_Node3-Ryzen7-5700G
Block graffiti                  ProductGuy

Relevant log output

Found share: 0000000001ad07bd 93323 65.74 MH/s
Found share: 00000000186f1664 93345 69.94 MH/s
Hashrate... \ 67.06 MH/s (67067951)

<--- Last few GCs --->

[16928:0000024EB1844E60] 506494131 ms: Scavenge 46.0 (57.4) -> 45.1 (57.4) MB, 0.5 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure;
[16928:0000024EB1844E60] 506499261 ms: Scavenge 46.0 (57.4) -> 45.2 (57.4) MB, 0.4 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure;
[16928:0000024EB1844E60] 506504385 ms: Scavenge 46.1 (57.4) -> 45.3 (57.4) MB, 0.6 / 0.0 ms  (average mu = 1.000, current mu = 1.000) allocation failure;


<--- JS stacktrace --->

FATAL ERROR: Committing semi space failed. Allocation failed - JavaScript heap out of memory
 1: 00007FF7EBC99E7F
 2: 00007FF7EBC20C06
 3: 00007FF7EBC21FC2
 4: 00007FF7EC6BA214
 5: 00007FF7EC6A5572
 6: 00007FF7EC5273CC
 7: 00007FF7EC53182C
 8: 00007FF7EC523E67
 9: 00007FF7EC4CB205
10: 00007FF7EBBB3D03
11: 00007FF7EBBB26A6
12: 00007FF7EBCF5E8B
13: 00007FF7EBCF59D2
14: 00007FF7EBCC80B5
15: 00007FF7EBBD7118
16: 00007FF7EBC5BE91
17: 00007FF7EBC5D625
18: 00007FF7EBA6771C
19: 00007FF7ECC8DC28
20: 00007FFFB73B26BD BaseThreadInitThunk+29
21: 00007FFFB95EA9F8

Graffiti

ProductGuy

@crProductGuy crProductGuy added the bug Something isn't working label Apr 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant