Closed
Bug 1109119
Opened 10 years ago
Closed 10 years ago
win7sp1: after 2.30 to 2.31 upgrade, SeaMonkey crash
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1092810
People
(Reporter: daniele.bonini, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0 SeaMonkey/2.30
Build ID: 20141013232806
Steps to reproduce:
After the upgrade from SeaMonkey 2.30 to 2.31, launching the browser crash immediately with report window.
my configuration:
Win7sp1 in VirtualBox 3.4.18 for Linux
I use a remote location for the profile, on a mapped folder
plugins installed:
-noscript
-downthemall
-displaymailuseragent
-chatzilla
Actual results:
SeaMonkey startup crash
Expected results:
expected behavior
Reporter | ||
Updated•10 years ago
|
Summary: win7sp1: after 2.30 to 2.31 to upgrade, SeaMonkey startup crash → win7sp1: after 2.30 to 2.31 to upgrade, SeaMonkey crash
Reporter | ||
Updated•10 years ago
|
Summary: win7sp1: after 2.30 to 2.31 to upgrade, SeaMonkey crash → win7sp1: after 2.30 to 2.31 upgrade, SeaMonkey crash
DUP of Bug 1092810 - Crash after migration data from Seamonkey v.2.30 Final to Seamonkey v2.31 Beta 1 Build 1 [@ nsRDFPropertyTestNode::FilterInstantiations(InstantiationSet&, bool*) const ]
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•