Hi @oschwald
When I am in a situation with high concurrency and slightly insufficient CPU resources, occasionally an unexpected fault address issue occurs, leading to a panic.
This kind of memory-level error makes it impossible for recover to catch it.
Below is the stack information I found, which ultimately points to the readLeft method. Can you help take a look or is this a known issue?
Hi @oschwald When I am in a situation with high concurrency and slightly insufficient CPU resources, occasionally an unexpected fault address issue occurs, leading to a panic. This kind of memory-level error makes it impossible for recover to catch it.
Below is the stack information I found, which ultimately points to the readLeft method. Can you help take a look or is this a known issue?
Thank you very much.