internal: Increase worker thread stack and name them

[lnicola]

CC #11370

[ivan]

Thanks! I confirmed that this fixes the stack overflow I mentioned in #11370 (comment). I did not have to disable cache priming.

I built rust-analyzer with full lto and tested https://github.com/ludios/ra-chalk-overflow-bug-2 with the default CHALK_SOLVER_ values.

[lnicola]

Thanks!

@bors r+

[bors]

📌 Commit 0b9cd8a has been approved by lnicola

[bors]

⌛ Testing commit 0b9cd8a with merge 6d3396a...

[ivan]

It looks like a 3MB stack size is also enough to avoid segfaults with https://github.com/ludios/ra-chalk-overflow-bug-2. (Though I now see finding the minimum value doesn't matter because it's virtual memory.)

[bors]

☀️ Test successful - checks-actions
Approved by: lnicola
Pushing 6d3396a to master...

[ntn-x2]

When will this be included in a release? (Having the same issue with our blockchain repo https://github.com/KILTprotocol/kilt-node)

[lnicola]

It's already included in the latest release, but it doesn't seem to solve the issue completely (see #12484).

[ntn-x2]

Can confirm that. I just switched to nightly and I still have the same issue.

[lnicola]

As a workaround, you could try reducing CHALK_SOLVER_MAX_SIZE to 100 or so, but I haven't tested it. Unfortunately, that doesn't help with #12484.