memory allocation of bytes failed[Bug]

[Mywifi]

🐛 Bug Report

2022-11-17T05:34:32.786756Z DEBUG Proving 'CoinbasePuzzle' (Epoch 175, Block 44988, Coinbase Target 9246809, Proof Target 72241)
2022-11-17T05:34:32.786798Z DEBUG Proving 'CoinbasePuzzle' (Epoch 175, Block 44988, Coinbase Target 9246809, Proof Target 72241)

2022-11-17T05:34:32.835473Z DEBUG Proving 'CoinbasePuzzle' (Epoch 175, Block 44988, Coinbase Target 9246809, Proof Target 72241)

2022-11-17T05:34:33.956821Z TRACE Prover solution was below the necessary proof target (2 < 72241)

2022-11-17T05:34:33.963318Z TRACE Prover solution was below the necessary proof target (1 < 72241)

2022-11-17T05:34:33.977242Z TRACE Prover solution was below the necessary proof target (1 < 72241)

2022-11-17T05:34:34.117943Z DEBUG Proving 'CoinbasePuzzle' (Epoch 175, Block 44988, Coinbase Target 9246809, Proof Target 72241)

2022-11-17T05:34:34.121948Z DEBUG Proving 'CoinbasePuzzle' (Epoch 175, Block 44988, Coinbase Target 9246809, Proof Target 72241)

2022-11-17T05:34:34.131004Z DEBUG Proving 'CoinbasePuzzle' (Epoch 175, Block 44988, Coinbase Target 9246809, Proof Target 72241)

2022-11-17T05:34:36.219320Z TRACE Prover solution was below the necessary proof target (4 < 72241)

2022-11-17T05:34:36.240890Z TRACE Prover solution was below the necessary proof target (1 < 72241)

2022-11-17T05:34:36.288022Z TRACE Prover solution was below the necessary proof target (2 < 72241)

2022-11-17T05:34:36.294790Z TRACE Prover solution was below the necessary proof target (1 < 72241)

2022-11-17T05:34:36.315004Z TRACE Prover solution was below the necessary proof target (1 < 72241)

2022-11-17T05:34:36.327221Z TRACE Prover solution was below the necessary proof target (1 < 72241)

2022-11-17T05:34:36.869599Z TRACE Prover solution was below the necessary proof target (3 < 72241)

memory allocation of memory allocation of memory allocation of memory allocation of memory allocation of memory allocation of memory allocation of memory allocation of 524288524288524288524288524288 bytes failed
 bytes failed
524288 bytes failed
 bytes failed
 bytes failed
 bytes failed
524288524288 bytes failed
 bytes failed

Steps to Reproduce

running for a while, sometimes it show this logs and stop proving

Your Environment

• build with commit8a747a7e9068df6cf6b7bed9cebbd63c7f66cbbd
• rustc 1.65.0 (897e37553 2022-11-02)
• cargo 1.65.0 (4bc8f24d3 2022-10-20)
• Windows Server 2019 standard(1809)
• AMD Ryzen 9 3900X 12-Core Processor
• RAM 32GB
• DISK 111GB with 76.5 empty

[HarukaMa]

This could be the heap fragmentation issue as well. Is there any downside to use jemalloc by default on supported platforms?

[ljedrz]

I've considered this too; if the pending fixes for the address resolver issues don't patch the leaks we've been seeing (which they do for me locally), I will be recommending using jemalloc.

[ljedrz]

Closing, as we've switched to using jemalloc by default.