Hi,
On 15.02.2013 16:13, Rob Weir wrote:
On Fri, Feb 15, 2013 at 9:53 AM, Oliver-Rainer Wittmann
[snip]
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.
I wasn't sure either. The question is whether the quick start is
terminated in all cases when doing install? Or are there cases where
it would still be running, causing it to hang on to some profile
files? In that case a reboot would clean that up.
Yes, the Quick Starter.
I would expect that it terminated on Uninstallation.
And yes, a running Quick Starter more or less "locks" the user profile -
step 3) would not work completely.
Best regards, Oliver.
