Václav Haisman

Take a look at PR #491, if it does not help with your case. It makes the thread pool optional (still enabled by default).

The thread pool is there so that any Appender can be made asynchronous. If you do not mind that you will lose this capability, you can disable the thread pool.

[**@leventov**](https://github.com/leventov) commented on [Jun 14, 2018, 7:56 PM GMT+2](https://github.com/log4cplus/log4cplus/issues/316#issue-332504062 "2018-06-14T17:56:50Z - Replied by Github Reply Comments"): > Please use read-write lock, such as `std::shared_mutex`, here: https://github.com/log4cplus/log4cplus/blob/936213586d3f5190f803e76da606a54ae3120c89/include/log4cplus/hierarchy.h#L299 It guards mostly read-only...

I have changed the mutex type on branch [master-make-hashtable-mutex-rw-lock](https://github.com/wilx/log4cplus/tree/master-make-hashtable-mutex-rw-lock) to `SharedMutex`, if you want to benchmark it.

[**@leventov**](https://github.com/leventov) commented on [Jun 15, 2018, 2:45 PM GMT+2](https://github.com/log4cplus/log4cplus/issues/316#issuecomment-397609318 "2018-06-15T12:45:57Z - Replied by Github Reply Comments"): > > Do you have any numbers from a benchmark? > > I did...

Please use English to report issues.

Also, use commit messages only in English.

What version of log4cplus are you using? Is log4cplus.dll loaded as a dependency of another DLL that is loaded using `LoadLibrary()`?

Could you please try and provide call stack of the stuck thread?

I do not have access to Visual Studio on Windows any more. Do you have any suggestion for a fix? As far as I can see, the `tstring.h` looks correct....