Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | -invisible causes hang at loadComponentFromURL() | ||
---|---|---|---|
Product: | udk | Reporter: | jameslee <lista> |
Component: | code | Assignee: | andreas.schluens |
Status: | CLOSED FIXED | QA Contact: | issues@udk <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues |
Version: | OOo 1.0.0 | ||
Target Milestone: | --- | ||
Hardware: | Sun | ||
OS: | Solaris | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
jameslee
2002-05-14 11:19:36 UTC
This seems to be yours? MBA->AS: Please have a look, if this bug is reproducable, we should fix it in the next release. Sorry - not reproducable. Please provide mor informations. - which office build? - may a stack trace, which shows the office side at this time - your full java code - use you the office bean ? Please note: FrameSearchFlag.AUTO isn't supported realy. Because it's not a valid combination of right search flags. If you say - your call works fine (if invisible isn't used) so I mention you use "_blank" as "Site.Frame". Is it true? If "Site.Frame" is a valid name of an already existing frame (e.g. "myFrame01") then you must use CHILDREN instead of AUTO. Otherwhise I think your call must fail everytime. But thats not a reason for a deadlock. Sorry - I couldnt reproduce this behaviour. Using your last provided java example runs for more then 2000 cycles without any problems. seen on a windows pc (1 cpu) and an ultra sparc 80 (2 cpu) tested with and(!) without -invisible tested with word, writer and other documents I've forwarded this bug to our internal API testing. But if they doesnt find anything too - we must close this bug as "non reproducable". Andreas->James Lee: Please provide some stacks from office side which may show a deadlock or some other strange things. I found the problem. We have a special feature - a quit timer, which tries to terminate the application if last windows was gone. This timer runs 5 sec and checks for new opened documents. But on using large documents this time isn't may be enough. Solution: Disable this fetaure (means the timer) for an office, which runs in mode "-invisible" & "-server". In this case the outside user has to finish the application. Workarounds: 1) Open an empty document which hold the application alive 2) be frame::XTerminateListener on the desktop instance to hinder the application on shutdown 3) use the same frame for all open documents WITHOUT(!) closing it I`ve disabled the quit timer for some further command line arguments. We fixed it for our internal version srx643 j and was able to load more then 1000 documents without any crash or deadlock. Of course it may depend from the used documents. But in general it should work now. |