You're migrating a profile from NS 4.61 to SM current by doing
NS-->Mozilla-->SM1-->SM2-->SMcurrent.
SM2 = SMcurrent, SM1 = older version of SM which should
unconditionally be able to e.g. import old NS mails. After the problem
occurs FF will be affected too, so it isn't SM-specific.
This was the historical natural order of use (without problems), so
it's just an attempt to avoid the error condition during an install of
the OS. Now it seems to be relared to add-ons. Earlier it looked like
it was related to using SM before Mozilla/NS.
You should actually use SM2.1 instead of SM2 and shouldn't need
the Mozilla and SM1 steps.
Thanks, so we can ignore all of the steps above. I've never reproduced
the problem without extra steps, but there's no reason to not agree
with you.
Afterwards you install 2 add-ons, get a crash and then 100%CPU
Yes, at least the last (and best "recorded") time.
Sometimes FF/SM has to be restarted to activate/use a new add-on, and
sometimes not. I should have restarted FF/SM after each install, but I
didn't. SM, still fast, crashed during the install of the second
add-on, before it was restarted.
but on only one of 2 identical machines.
Digital mirrors aren't identical. You can e.g. visit the /pub/incoming
directory of a Hobbes mirror to find wrongly uploaded files. The
operator of the NMSU may have deleted uploaded files, but the mirror
didn't. Setups should be identical.
You have tested safe-mode and it didn't help and you have not
tested a new profile for comparison.
Yes, no. I'm using "DELTREE" to delete profiles, and I've used both a
new profile and (at the moment) a copied profile. If a nachine wasn't
affected, the the copied profile works as expected. If a machine was
affected, then it will still be affected.
So the profile files shouldn't play a role, unless there's code which
changes the profile first, even before the --safe-mode dialog is
displayed.
When I'm talking about a copied working profile, then I'm talking
about everything under a "<passwordy>.default"-directory.
You don't have an extensions directory anywhere even after
installing add-ons.
Not anywhere.
x:\HOME\DEFAULT\Mozilla\Extensions
x:\HOME\DEFAULT\Mozilla\Firefox\Profiles\3ozcttvn.default\extensions
x:\HOME\DEFAULT\Mozilla\SeaMonkey\Profiles\1hntxk0z.default\extensions
x:\HOME\DEFAULT\Mozilla\SeaMonkey\Profiles\1hnmxy0z.default\extensions
\inspect
***@mozilla.org\chrome\inspector\content\inspector\extensions
y:\Apps\Firefox\browser\extensions
y:\Apps\SeaMonkey\extensions
y:\Apps\SeaMonkey\distribution\extensions
(working directory structure, but that shouldn't matter, I've manually
compared the first, identical directory and all other entries should
be mirrors)
The first directory is empty, an empty directory excluded. Numbers 2-4
belong to a copied, working profile. Installing SM again never helped
(entries 5-7).
Should I try to (fully) copy a working profile and to reinstall the
distributed SM-package before starting SM?
Does about:addons show any installed?
AFAICT everything works, e.g. the language pack. I'm trying
about:addons now...
--safe-mode first: after 10 seconds (IBM ThinkPad X20) the CPU-load
becomes 100%. After (a less meaningful, due to the slowlyness) 70
seconds the Safe Mode-dialog is displayed. Exit (dialog): CPU load
remains 100% during 5 seconds.
Unsafe again, about:addons and after several minutes: everything is
installed, including a dictionary and the langpack.
Have you tried moving addons.sqlite out of your profile?
I have now. No change, as expected. FF, a different profile, is
affected too. It looks like a generic file or setting is involved.
Or perhaps one generation of notebook CPUs, combined with add-ons?
Some mirrors:
IBM ThinkPad 600E (Pentium II): works
IBM 300 PL (Pentium III, desktop): works
IBM ThinkPad 600X (Pentium III): slow
IBM ThinkPad X20 (Pentium III): slow
IBM ThinkPad T23 (Pentium III-M): works
IBM ThinkCentre A30 (Pentium IV, desktop): works
IBM ThinkPad T42p (Pentium IV): works
X20 (slow) & your CPUInfo utility, FWIW:
vendor_id GenuineIntel, cpu family 6, model 8, stepping 6, flags fpu
vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx
fxsr sse, cpu MHz 609.663, model name Intel(R) Pentium(R) III
processor.
BTW, it's hard to actually reproduce the problem because a full new
install of the OS may be required. Just reinstalling SM won't help,
AFAICT. Nor does using a working profile. I didn't record the add-on
which crashed nor the order of add-ons before the install was
affected. I didn't change CONFIG.SYS nor plugins. The virtual page 803
of my install manual just reads "install all FF and SM add-ons".
--