Paulo Dias wrote:
>
> any light on this strange behaviour is welcome...
There are essentially two things that mozilla does on first launch that
it doesn't do afterwards:
1) Creates various files in bin and bin/components: mozregistry.dat,
component.reg and xpti.dat;
2) Creates and copies files to the profile tree.
Disabling these items one at a time after the first run should indicate
if any of them is to blame.
I also vaguely recall encountering a similar launch hang a while back
when I tried running two different versions of Warpzilla with the same
Users50 tree,
h~
