Hello Xiaofei, (I *really* hope I got the salutation right this time :). The habit in this list - and all other OOo lists I know - is to address the oner person with the first name, so I hope you don't mind.)
> Thanks very much for your reply, duyunfen has Fwded it to me, we have > tracked the bug but the deadlock seem to occur somewhere among windows' > system processes, here is how the Call Stack looks at a point when the > phenomenon happens: > > > user32.dll!77d191be() > user32.dll!77d191f1() > ole32.dll!769c375e() > ole32.dll!769d70d5() > ole32.dll!769d7008() > ole32.dll!769ae3dc() > ole32.dll!769ae444() > kernel32.dll!7c80b683() That's only one thread. A deadlock nearly always involves two threads, seldom only one, more seldom more than two). So, you definitely need the stacks of the other threads. > P.S. duyunfen's real name is Du Yunfen, with family name Du, and it's a > "her name" rather than "his name". ;-) Oops :) Didn't know this, sorry, but will respect it in the future. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
