Apache OpenOffice (AOO) Bugzilla – Issue 38213
[src680 m64] crash when open database beamer or Bibliography component
Last modified: 2006-05-31 14:29:06 UTC
1. open a new document 2. press F4 ==>> crash
fs->mav: This looks like a problem with the new file storage implementation. I'm going to attach a stack
Created attachment 19961 [details] stack of the crash
The file system storage seems to catch an exception while retrieving storage names, and re-throw it as WrappedTargetRuntimeException - which is nowhere caught. Several things came to my mind when seeing this: - framework should be more exception-resistent against exceptions in components it faciliates. However, that's definately not the primary problem here - I am not sure about wrapping an non-RuntimeException as WrappedTargetRuntimeException. Basically, a RuntimeException means "something went extraordinarily wrong, no chance to recover from this". Thus, RuntimeExceptions are seldomly caught. However, when the storage now wraps a non-RuntimeException as (WrappedTarget)RuntimeException, then it promotes a possibly non-fatal error to a fatal error - as it seems to happen in this case. I tend to think that this is a questionable concept, in general. In this particular case, is it possible that getElementNames is allowed to fail, and perhaps should simply return nothing?
The problem is fixed.
*** Issue 38221 has been marked as a duplicate of this issue. ***
found another manifestation: Tools|Bibliography (in a text document) crashes with the very same stack. Seems it's a general problem with non-SFX frames ...?
*** Issue 38216 has been marked as a duplicate of this issue. ***
the Tools|Bibliography problem is also fixed with this - great!
The problem was that the broken storage based on nonexistent folder was created. Now the correct checking is done on readonly storage creation. The framework code accesses shared UI configuration using readonly access. So if there is no configuration for an application ( seems to be the case for database ) the problem is reproducible.
*** Issue 38229 has been marked as a duplicate of this issue. ***
Ropening to send for verification.
Please verify the issue.
Setting back to fixed.
verified in master
close