Issue 22717 - DllMain(PROCESS_DETACH) problems with sal's static C++ objects
Summary: DllMain(PROCESS_DETACH) problems with sal's static C++ objects
Status: CLOSED FIXED
Alias: None
Product: udk
Classification: Code
Component: code (show other issues)
Version: OOo 1.1
Hardware: PC Windows XP
: P2 Trivial (vote)
Target Milestone: OOo 1.1.1
Assignee: Olaf Felka
QA Contact: steffen.grund
URL:
Keywords: oooqa
Depends on:
Blocks: 21809
  Show dependency tree
 
Reported: 2003-11-21 15:25 UTC by Daniel Boelzle [:dbo]
Modified: 2010-10-22 19:32 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
After finish button I got this error when installing OOo 680m17. Still exist/not yet solved (8.29 KB, image/gif)
2003-12-17 10:31 UTC, utomo99 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Daniel Boelzle [:dbo] 2003-11-21 15:25:49 UTC 
sal DllMain(PROCESS_DETACH) is called _before_ sal's static de-initializers are
called.
Potential workaround: a static C++ object in DllMain()'s PROCESS_ATTACH block
and empty PROCESS_DETACH block, thus the object is added first to the
de-initializer list.

closing 21809 which is duplicate to this one which is targetted towards OOo 1.1.1.
Comment 1 Daniel Boelzle [:dbo] 2003-11-21 15:32:37 UTC 
*** Issue 21809 has been marked as a duplicate of this issue. ***
Comment 2 hennes.rohling 2003-11-24 14:26:00 UTC 
On process exit DllMain() is called *before* C and C++ Runtime
(including static destructors) is shut down.
Comment 3 hennes.rohling 2003-12-11 15:36:11 UTC 
Fixed in cvs/porting/sal/osl/w32/dllentry.c on branch cws_fix645_sal7pp2
Comment 4 utomo99 2003-12-17 10:30:01 UTC 
This problem didnt happend in OOo 1.1.
but happend in all OOo 680 build. til m17 still same problem. 
I will attach the screenshot from OOo 680 m17 which I just installing it.
Comment 5 utomo99 2003-12-17 10:31:49 UTC 
Created attachment 11990 [details]
After finish button I got this error when installing OOo 680m17. Still exist/not yet solved
Comment 6 hennes.rohling 2003-12-17 10:36:47 UTC 
Please be patient. The fix is done on the branch I specified. It will be merged
into master for 645 and 680 builds. Then the issues will be set to
"Verified/Closed".

The bug is a general problem that may also occur in 645 (OOo 1.1 build) and we
already got crash reports reporting that problem for 645.
Comment 7 utomo99 2003-12-17 10:53:24 UTC 
utomo > hro:
Thanks. sorry I test this, ebcause I got info from my issue which is reported 
in OOo680, but ask me to verified that and close. 
I will wait, including next 680 version, I will try if possible.
Comment 8 hennes.rohling 2003-12-18 13:28:06 UTC 
hro@of: Please verify.
Comment 9 hennes.rohling 2003-12-18 13:32:26 UTC 
hro@utomo: Olaf Felka can only verify if the changes I made did not break OOo
1.1.1 because the error isn't reproducable on OOo 1.1.0 (but did occur under
some special circumstances).

So I'd like to ask you to close this task after the fix made it into 680. If
Olaf set the task to "Verified" it does notmean that the changes are already
merged into src680.

Please use cvs log to determine when the change are merged into 680.
Comment 10 Olaf Felka 2003-12-18 15:34:20 UTC 
of: Tested on WinXP and 98.
Comment 11 Olaf Felka 2003-12-18 15:35:28 UTC 
Verified in cws sal7pp2.
Comment 12 utomo99 2003-12-24 04:32:30 UTC 
I tried OOo 1.1.1a, and didnt occur (however, I _Didn't_ have this problem in 
_All_ my 1.1 version)

But I _Always_ get this problem in _All_ OOo 2.0 version, so to make sure I 
need to test OOo 2.0 version. 
Thanks.
Comment 13 Olaf Felka 2004-01-28 09:53:47 UTC 
Ok in 680m20.
Comment 14 Unknown 2010-10-22 19:32:06 UTC 
Created attachment 72202