Hi,
On 15.02.2013 15:06, Rob Weir wrote:
On Fri, Feb 15, 2013 at 8:37 AM, Oliver-Rainer Wittmann
<orwittm...@googlemail.com> wrote:
Hi,
On 15.02.2013 13:52, Rob Weir wrote:
On Fri, Feb 15, 2013 at 6:53 AM, Oliver-Rainer Wittmann
<orwittm...@googlemail.com> wrote:
Hi,
I would like to draw your attention on issue 121625 [1] - a tracking
issue
for the crashes which had been reported in Bugzilla and in the forum (as
I
know from Hagar) which occur right a couple of seconds after the
application
start.
I was able to reproduce such crashes - for details have a look at the
issue.
Due to two viral flues which knocked me out for all together more than
two
weeks it took some time to find the root cause.
I think I have found it - again look at the issue for details.
I will commit a patch to avoid such crashes in the future.
How many issues do we have that cause a random crash?
I thought there were two different issues:
1) Profile corruption
2) Checking for extension updates
Is this uncaught exception issue a new one? Or is it the root cause
of one (or both) of the above two issues?
It seems I need to be more verbose here on the list ;-)
It is the root cause for both which are more or less the same.
A user profile corruption in the extension databases causes crashes when
checking for extension updates. Extension updates can be triggered manually
or automatically as part of the checking for an application update.
OK. So this is a very good outcome, if it is a single root cause and
we have a good fix and workaround.
I'd like to make a Youtube video to show how to fix this issue in
existing installations, but the steps are not clear.
For example, in the issue you say, "The problem persists even, if the
user profile has been renamed/removed". But then your solution is to
delete two files from the profile:
$USERPROFILE/3/user/extensions/bundled/extensions.pmap
$USERPROFILE/3/user/extensions/bundled/extensions.db
So why doesn't deleting the whole profile work?
On the first startup after the user profile had been renamed/removed the
user profile is recreated and due to the existing bundled extension
folders in the installation
$USERPROFILE/3/user/extensions/bundled/extensions.pmap has been
recreated containing entries for these bundled extensions.
I observed that deleting this file after the user profile had been
recreated helps to prevent the crashes.
I'm trying to think of a fool-proof way for users to fix this, one
that eliminates possibilities of open or locked files. So maybe
something like:
1) Uninstall AOO
2) Reboot
3) Delete profile directory
4) Reinstall
Would that work?
I think this would work - I am not sure, if step 2) is needed.
The installation containing the "half" removed bundled extensions from
former OOo installation will be removed by step 1). The user profile
corrupted regarding its extension database will be removed in step 3).
But the user will lose all her/his user settings.
Thus, the workaround is something to keep as much as possible to prevent
the crashes.
Or do we still have an issue if new extensions are installed?
I am not sure, but I do not know of problems with newly installed
extensions causing such crashes.
Best regards, Oliver.
I have also given a workaround in the issue which someone could document
in
the forum as well. (As I had already discussed this workaround in another
thread with Hagar may be this has been already done.)
[1] https://issues.apache.org/ooo/show_bug.cgi?id=121625
Thanks for your attention.
Best regards, Oliver.
