Opened 13 years ago

Closed 12 years ago

#3652 closed Bugs (invalid)

App Verifier issue found in boost 1.33.0 thread library while unloading DLL

Reported by: ravisingh_id@… Owned by: Anthony Williams
Milestone: Boost 1.42.0 Component: thread
Version: Boost 1.34.0 Severity: Problem
Keywords: thread DLL unload Appverifier Cc:

Description

DLL built using boost 1.33.0 thread libraray has Appverifier crash while unloading.

======================================= VERIFIER STOP 00000202 : pid 0x15A4: Freeing heap block containing an active critical section.

06762FE0 : Critical section address. 004D2654 : Critical section initialization stack trace. 06762FC0 : Heap block address. 00000040 : Heap block size.

=======================================

In file …\boost_tp\boost\libs\thread\src\tss_hooks.cpp

on_process_enter() function calls init_threadmon_mutex()acquires memory for mutex by executing threadmon_mutex = new boost::mutex; statement. However, this memory is not released when dll in unloaded. I guess the acquired memory should be released in on_process_exit() call.

Is this a known issue and is there any fix for this?

This problem was also found in 1.34 version

Change History (3)

comment:1 by viboes, 13 years ago

Component: threadsthread
Summary: App Verifier issue found in boost 1.0.33 thread library while unloading DLLApp Verifier issue found in boost 1.33.0 thread library while unloading DLL

Boost.Thread has completely redesigned since version 1.35. Have you checked with the last release?

in reply to:  1 comment:2 by ravi singh <ravisingh_id@…>, 13 years ago

Replying to viboes:

Boost.Thread has completely redesigned since version 1.35. Have you checked with the last release?

No, I have not checked with the latest release. Since our code is based off 1.33, so I am just checking the compatable boost versions and this is not fixed in 1.34. Higher versions have lot of new interfaces and my old code will not work with that.

I would be interested in getting this fixed in either 1.33 or 1.34 as a patch.

btw - has this issues been faced by some one else?

comment:3 by Anthony Williams, 12 years ago

Resolution: invalid
Status: newclosed

Bug relates to pre-1.35 rewrite

Note: See TracTickets for help on using tickets.