Modify

Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#4606 closed Bugs (fixed)

[flyweight] test_intermod_holder regression test failure on Windows

Reported by: rwebb <richard.webb@…> Owned by: Ion Gaztañaga
Milestone: To Be Determined Component: flyweight
Version: Boost Development Trunk Severity: Problem
Keywords: Cc:

Description

When running the regression tests on Windows XP i see the test_intermod_holder.exe regression test process hanging around (it doesn't complete, and the test system doesn't terminate it).

If i run the test in the VC9 debugger, it goes into the call to pIWbemLocator->ConnectServer? in get_wmi_class_attribute (win32_api.hpp) and never returns (at least not in a reasonable timeframe). All of the Windows based test runners seem to have the same issue.

I don't know why this happens though.

Attachments (0)

Change History (3)

comment:1 Changed 7 years ago by Joaquín M López Muñoz

Component: flyweightinterprocess
Owner: changed from Joaquín M López Muñoz to Ion Gaztañaga

Changed component to interprocess, as per discussed in http://thread.gmane.org/gmane.comp.lib.boost.devel/208308

comment:2 Changed 7 years ago by Ion Gaztañaga

Resolution: fixed
Status: newclosed

Updated Interprocess so that intermodule_singleton uses windows native shared memory.

comment:3 Changed 7 years ago by Joaquín M López Muñoz

Component: interprocessflyweight

Changed the component back to flyweight, since this most accurately matches with the ticket's original description and further development. As of changeset 65927 intermodule_holder is not based on boost::interprocess::named_mutex and relies instead on Boost.Interprocess internal intermodule_holder, which is not affected by the hanging problem on DLL loading time. Thanks to Ion for his work on solving this out.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Ion Gaztañaga.
The resolution will be deleted.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.