Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
0.10.0
-
None
-
None
-
WinXP 64 bit
Description
Each call to configureAndWatch causes a new FileWatcher object to be created (without deleting the old one) and consequently a new thread to be created (even though the old one may still be running).
This means that it's very unsafe to call configureAndWatch more than once (and even when calling it just once, it leaks soem mem and a thread).
Attachments
Attachments
Issue Links
- is related to
-
LOGCXX-390 xml::DOMConfigurator::configureAndWatch leaks memory and threads like LOGCXX-342
- Resolved