To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=78284
------- Additional comments from [EMAIL PROTECTED] Sat Jun 16 19:03:27 +0000 2007 ------- Hi, for some (certainly discussable,let me know if you are interested) reason, the pyuno bridge needs a separate thread to release python objects (and thus potentially uno objects as it is the case in the callstack given above). This can lead to crashes at process termination, because the race between "regcomp releases all loader/factory objects and terminates main()" and "pyuno-gc-thread release call" is not solved. The "static destructor guard" worked for my earlier problems, but it can't avoid the core race, so when it hits you now, it might be, that you cant find a compiler switch, which will make it work. The urp remote bridge had (and may have it still, dont know) the same problem (see urp_environment.cxx and g_bStaticDestructorsCalled). The crash can be avoided 1) (easy and dirty) terminating regcomp with _exit() 2) introduce a process termination synchronization API eg. in sal, which can cleanly solve the races, here changes in regcomp (and all other uno executables which currently dare to terminate with exit()), sal and pyuno are necessary. But as everyone, who uses a thread as implementation detail in the uno world has the same problem, it might be the way to go. Bye, Joerg --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
