Andreas Bröker wrote: > Hello Mathias, > > the posted code is only an example in order to reproduce the > OpenOffice.org crash with a great many of API calls. In real life > code with also a huge amount of API calls. But i think it is not a > good idea to write down here 10000 LOC. Therefore i asked not for > workaround not the loop - i asked for a workaround in order to > prevent the OpenOffice.org crash. Sorry for that misunderstanding.
So you want a general workaround to avoid crashes? That's like the answer to all any everything - and you probably already know that this is "42". :-) Seriously now, a workaround for a particular crash can't be given before the root cause is known. As Stephan pointed out, we meanwhile know the culprit and for your example code there is no possible workaround. And of course you don't need it because it is "artificial" code. Wether a workaround is possible in your application can't be judged without knowledge of the source code. And as you stated correctly, this is not the place to show 10000 LOC. Perhaps you can find a workaround by yourself now as you know the culprit. It seems as if you should make sure that before you create "the same" object a second time you must make sure that its first instance is destroyed already. But this is only a rough guess because I don't know your application. Best regards, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
