818334 - Reverting from >= 2.15 to <= 2.14 using a Profile that originated <=2.14 may result in a browser hang

Status: RESOLVED WONTFIX

(SeaMonkey :: General, defect)

Description

[therube]

Two ZIP'd profiles for analysis.

One, 21.dumy.hangs.2.14.ZIP from an XP system
The other 21.dumy3.hangs.2.14.ZIP from a Win7 system.

Both will freeze (AppHang) when attempting to open in SeaMonkey 2.14.
Both open successfully in SeaMonkey 2.15.

Comment 1

[therube]

Attachment: ZIP'd Profile

Comment 2

[therube]

Attachment: ZIP'd Profile3

Comment 3

[therube]

Attachment: WhatIsHang Text Report

Comment 4

[therube]

Windows Event Viewer Log:

The program seamonkey.exe version 17.0.0.4705 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
 Process ID: 4eb0
 Start Time: 01cdd285d090209b
 Termination Time: 16
 Application Path: C:\TMP\SEA\SM214.release\seamonkey.exe
 Report Id: 3afff2f4-3e79-11e2-a0a6-001966102012

Comment 5

[therube]

Another report, http://forums.mozillazine.org/viewtopic.php?p=12519557#p12519557

"2.15b opened ... I just shut it down and reverted to my "old" V2.11... or tried to. When I opened it it hung, then became "unresponsive" and hung up. Tried opening dirctly fm file; same. Had to C>A>Del to close it."

Comment 6

[therube]

We /may/ be able to generalize this as Core as FF 17 will also hang where FF 20 (as it was) opens successfully.

I say may, only because the Profiles originated from SeaMonkey.

I renamed sessionstore.json to sessionstore.js when copying over to FF.

Depending on the particular test Profile, that hang may not occur until you answer the Session Restore prompt (about:sessionrestore, perhaps twice in sucession) to restore the profile.

Comment 7

[Philip Chee]

I think this bug is pretty obsolete by now.