Issue 41917 - disposed exception with Desktop.terminate()
Summary: disposed exception with Desktop.terminate()
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: PC Linux, all
: P3 Trivial
Target Milestone: ---
Assignee: steffen.grund
QA Contact: issues@api
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-02 16:19 UTC by steffen.grund
Modified: 2013-02-24 21:07 UTC (History)
1 user (show)

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

Attachments
testcase (4.75 KB, application/x-compressed)
2005-02-02 16:26 UTC, steffen.grund 		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 steffen.grund 2005-02-02 16:19:13 UTC 
The attached test produces a disposed exception when Desktop.terminate() is called.
This only happens on Linux platform and with Kernel 2.6/KDE. The same test on
Kernel 2.4.2/KDE works.

To reproduce unzip the attached package, go to kernel26/complex/desktop and call
'dmake'
'dmake run OFFICE=</path/to/your/office/program>'
Comment 1 steffen.grund 2005-02-02 16:26:17 UTC 
Created attachment 22134 [details]
testcase
Comment 2 andreas.schluens 2005-02-10 12:40:30 UTC 
As you already mentioned ... this task is very hard to reproduce.
But it seems that this exception is not thrown by Desktop::terminate() itself.
A possible scenario:
a) Desktop::terminate() terminates the office (which is done synchronously of 
course ... because this method must return a state for success).
b) Termination of the office will close all open uno bridges ...
c) May the uno proxy of the java client side produces this exception. Because the 
bridge was already disposed.

For the moment this task cant be reproduced. So I will send it back to you.
May be it's a good idea to print out the stacktrace for this exception on java side 
(make it a part of the test itself) ... so we can may be found the real problem later, 
if the bug occures again.
Comment 3 andreas.schluens 2005-02-10 12:41:17 UTC 
.
Comment 4 steffen.grund 2005-03-23 17:47:14 UTC 
retarget: not reproducible.
Comment 5 steffen.grund 2005-08-18 13:32:08 UTC 
closed.