You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Heyo,
We are using the coralogix handler, version 2.0.5
So recently we implemented a feature which leverages multiprocessing in python, the feature raises a Pool of proceses. While in production we do not terminate in and restart the pool, if our tests we do that alot.
After implementing the feature, we say several cases where our processes will just hang transiently, upon investigation I was lucky to reproduce this bug locally, I saw there was a processes hanging ,using py-spy I looked at the dump of the process this find out:
It seems the process hangs in the coralogix http, looking at the code, it seems the specific line its hanging is cls._mutex.acquire(), therefore the hanging process is deadlocked with the main process. For now we have disabled coralogix in our CI
The text was updated successfully, but these errors were encountered:
Heyo,
We are using the coralogix handler, version 2.0.5
So recently we implemented a feature which leverages multiprocessing in python, the feature raises a Pool of proceses. While in production we do not terminate in and restart the pool, if our tests we do that alot.
After implementing the feature, we say several cases where our processes will just hang transiently, upon investigation I was lucky to reproduce this bug locally, I saw there was a processes hanging ,using
py-spy
I looked at the dump of the process this find out:The main process (waiting for the pool to die):
The hanging process:
It seems the process hangs in the coralogix http, looking at the code, it seems the specific line its hanging is
cls._mutex.acquire()
, therefore the hanging process is deadlocked with the main process. For now we have disabled coralogix in our CIThe text was updated successfully, but these errors were encountered: