New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logging is sometimes re-entrant #192
Comments
Is this still a problem? |
From brief look it seems a threading issue. See this StackOverflow question: https://stackoverflow.com/q/45680378/3648361 From the first look I couldn't understand whether we can fix it in |
It's a long time ago I investigated this. There have been some logging changes in NVDA related to comtypes, see nvaccess/nvda#14317 |
I don't think this issue is limited to I think @vasily-v-ryabov is right, it is a problem that occurs with asynchronous, parallelprocessing or multiprocessing. I am not in favor of eliminating logging from Your project PR seems to have accomplished not picking up any logs on the library side. What about this issue? |
Within NVDA, we use comtypes to access com objects. Until now, we ignored logging messages coming from comtypes. When I started investigating piping comtypes logging to the NVDA log, I noticed that NVDA crashed in a few minutes after enabling debug logging.
Here is an example traceback generated when comtypes logging is set to debug. It looks like some log messages generate another message that causes re-entrancy.
The text was updated successfully, but these errors were encountered: