Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
1.3 Final
-
None
Description
The first Call to be created remembers that it issued initialize_module and issues uninitialize_module in its destructor. Other Call objects don't issue initialize_module. If other Call objects are used after the first Call has been deleted, uninitialize_module will have been called and they will fall over. There should be a reference count of the number of Call objects and the last one should issue uninitialize_module, not the one that issued initialize_module. This problem will happen for Stubs and generated stubs, since a generated stub has a Stub and a Stub has a Call.