Abseil deadlock detection

[legendecas]

          > @targos: I wonder if it may be caused by https://github.com/nodejs/node/commit/96fde580b2227d49a2c935195ecf351f3e8bf099. I only rebased and added that commit.

I can reproduce the issue on a linux x64 machine in 3 out of 10 runs. I don't think it is related to nodejs/node@96fde58. The failure is an abseil deadlock detection based on the order of locked mutexes. This is only enabled on non-darwin platforms: https://github.com/targos/node/blob/1ed6e9890fd5dcf79489b54264f6dcf125b917fe/deps/v8/src/base/platform/mutex.h#L121-L125.

I doubt that if crash sites like https://github.com/targos/node/blob/1ed6e9890fd5dcf79489b54264f6dcf125b917fe/deps/v8/src/common/code-memory-access.cc#L149 are actual deadlocks. This could be a false-positive as the logs in https://ci.nodejs.org/job/node-test-commit-arm-debug/17748/nodes=ubuntu2204_debug-arm64/console suggest that the stack histories are from two distinct cctests.

Can we suppress abseil deadlock detection?

Originally posted by @legendecas in nodejs/node#57114 (comment)

[targos]

It seems to happen only in worker threads.

[legendecas]

The stack traces in https://ci.nodejs.org/job/node-test-commit-arm-debug/17748/nodes=ubuntu2204_debug-arm64/console are in the cctest main thread.