To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=114550
                 Issue #|114550
                 Summary|ExtensionManager "Check for updates" can crash on brok
                        |en user data
               Component|framework
                 Version|OOO330m7
                Platform|All
                     URL|
              OS/Version|All
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P2
            Subcomponent|code
             Assigned to|dv
             Reported by|cd





------- Additional comments from [email protected] Thu Sep 16 14:22:04 +0000 
2010 -------
It's possible that the ExtensionManager "Check for updates" can crash on broken
user data. A scenario is when you first use a Office installation which provides
a specific bundled/shared extension set. If you a different Office installation
with a different bundled/shared extension set and the lastsynchronized file has
a broken date/time then a unhandled com.sun.star.deployment.DeploymentException
can occur. This results in a terminated thread and the Office crashes.

See 
void UpdateDialog::Thread::execute()
{
...
}
where only a IllegalArgumentException is catched.

A much better error processing would be to catch the exception and provide a
meaningful error message to the user.

---------------------------------------------------------------------
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]

Reply via email to