346290 - Crash or hang on open on win95

Status: RESOLVED WONTFIX

(Toolkit :: Storage, defect)

Description

[JudyLambert]

User-Agent:       Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.8.1b1) Gecko/20060726 BonEcho/2.0b1
Build Identifier: Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.8.1b1) Gecko/20060727 BonEcho/2.0b1 Build ID 2006072801

Windows 95

With a virgin profile, branch build 2006072801, crashed on open with a KERNEL32.DLL failure.

Reference bug 329898 comment #26

Reproducible: Always

Steps to Reproduce:
Windows 95
1.Install Branch 2006072801 after using add/remove to delete old build.
2.Use profile manager to open FF with a new, empty profile in an empty folder previously created.
3.Start FF. See FF crash with KERNEL32.DLL error.

Comment 1

[JudyLambert]

Currently downloading an older nightly to see if I can get a Talkback for this.

Comment 2

[Masatoshi Kimura [:emk]]

Confirming.

Comment 3

[JudyLambert]

(In reply to comment #1)
> Currently downloading an older nightly to see if I can get a Talkback for this.
> 
Couldn't get a Talkback. System hang.

Comment 4

[Vladimir Vukicevic [:vlad] [:vladv] (needinfo me, slow to respond)]

There are two ways to fix this:

1) instead of explicitly specifying CP_UTF8 in os_win.c, use a global variable for this; on first init, check if we're on win95 and use CP_ACP instead of CP_UTF8.  This would allow users with ascii-only profile paths to continue to work, but would still break in the non-ascii case.

2) Do the same as above, but add in code somewhere (maybe in the calls to sqlite_open -- there's only one spot, in mozStorageConnection) to do the UTF8->codepage conversion, again, for win95 only (runtime check).  This assumes that we have code for that conversion in the tree already, which I'm not sure of.

Comment 5

[Fred Collier]

Somebody else said, "This appears to be the death knell for Windows 95 users for the sake of an obscure and esoteric Windows 9x problem".

Could this be true?

Comment 6

[Masatoshi Kimura [:emk]]

BTW SeaMonkey 1.1a started fine on Win95.

Comment 7

[Robert F. Ludwick]

I have been having FF hang on startup many times since upgrading to 2.0. Usually it hangs before the window ever opens, but once in awhile it hangs after the File and Navigation toolbars open, but before the Bookmarks toolbar opens.

Comment 8

[Jungshik Shin]

(In reply to comment #4)


> that we have code for that conversion in the tree already, which I'm not sure
> of.

I'm afraid we don't have UTF-8 -> codepage converter although we can do it via  UTF8 -> UTF16. (I don't know it's worth the effort because we only need it for 1.8 branch. Needless to say, that depends on whether we wanna support Win95 in 1.8 branch. ) The opposite was done in  

http://lxr.mozilla.org/seamonkey/source/nsprpub/pr/src/linking/prlink.c#1130

BTW, don't we need converters in both directions? 


Another BTW, UTF-32 in the comments in db/sqlite3/src/os_win.c should all be replaced by UTF-16. |WCHAR *| on Windows is not UTF-32 but UTF-16. 

Comment 9

[Robert Kaiser]

Currently, Firefox officially doesn't support Win95 on 1.8 branch. If it's easy to fix, it's always something nice to have though, esp. as SeaMonkey does support Win95 on 1.8 branch still and does ship with storage.
As SeaMonkey doesn't use storage itself though, it runs without problems, but extensions which try to use it will make the whole app unstable on Win95.

If someone comes up with a patch, I hope it will be taken as it can be important to have the 1.8 branch builds available for a longer time so that everyone on Win9x who can't upgrade to the post-1.8 world still has a secure browsing environment available to him. We've seen with unsupporting MacOS 8/9 that years after stopping to support it, people still ask for build that run on those, and we'll probably also see this with the much more widely used Win95/Win9x OSes.

Comment 10

[erpman1]

(In reply to comment #9)

> If someone comes up with a patch, I hope it will be taken as it can be
> important to have the 1.8 branch builds available for a longer time so that
> everyone on Win9x who can't upgrade to the post-1.8 world still has a secure
> browsing environment available to him. We've seen with unsupporting MacOS 8/9
> that years after stopping to support it, people still ask for build that run on
> those, and we'll probably also see this with the much more widely used
> Win95/Win9x OSes.
> 

so far, there is no patch that will make firefox 2.0 (or the 1.8.1 branch of FF) work correctly under Win95.  Don't bother waiting for one either.  Win95 users should consider using the latest release of FF 1.5 instead of FF 2.0.

Comment 11

[Shawn Wilsher :sdwilsh]

Sorry, this is a crash in an unsupported platform.  If someone comes along with a patch, we can reopen, but until then this is RESOLVED->WONTFIX.