Closed Bug 45067 Opened 22 years ago Closed 21 years ago

installing java with low diskspace seems to leave installer hung on win95

Categories

(Core Graveyard :: Java: OJI, defect, P3)

x86
Windows 95
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: chofmann, Assigned: James.Melvin)

Details

(Keywords: hang, relnote, Whiteboard: [nsbeta2-] relnote-user jpibug)

run the installer with low diskspace on the drive containing
win temp directory/swap file.

pick custom installer with all options selected..

install proceeds along seemingly ok until a
dialog box with "Configuring Sun Java 2, please wait"
is shown...

I wait, and wait, and wait, but it never comes back...
Norton shows CPU peg'd at about 94%, C drive space at 7.7MB available

VM goes under 13MB..

Finally end up needing to kill the install process to get a
chance at running the monkey in all its wonder.
This always happens on my laptop...  I hate this...
Keywords: nsbeta2
Wrong category.
I am moving this bug to OJI
Assignee: idk → drapeau
Component: Java-Implemented Plugins → OJI
Re-assigning to Stanley Ho, since this has to do with the JRE, not the Mozilla
OJI module.  Stanley?  Hit it!
Assignee: drapeau → stanley.ho
Chris, can you run the .exe file by hand.  Here is the command line that the 
installer uses:
  jre13i.exe  -s -a -s

you can find the .exe in the daily build directories ..\xpi.  Try two methods:
1) just "jre13i.exe" (will show UI)
2) "jre13i.exe -s -a -s" (will not show UI)

See if you get the same results as this bug.

ps. also 
1) what kinda of laptop do you have?
2) how much ram?
3) I see this bug is marked against Win95, but just to be sure, what OS are you 
running on it (any service packs too)?  If this is indeed Win95, can you run 
\\yatsura\bin$\w95debut.exe.  It will tell you if you have the first release of 
Win95 (the debute version) or not.
4) What's the longest time (that you can remember) waiting before killing the 
process?
Todays update:  - ran the complete install and it seemed to run fine.
The one difference in my configuration is a signficant amount
more diskspace on the installation target drive (d:)  In previous
attempts I was near the border on diskspace on that drive, but enough
space to allow the installation to continue...   I guess the thing
to test is low diskspace ( < ~20 MB on both the c:\windows\temp and
swap dir AND also on the installation target drive )

might be enough of a side case to defer past beta2.

Answers to other questions.

Here is the command line that the 
installer uses:
  jre13i.exe  -s -a -s

this ran fine.

you can find the .exe in the daily build directories ..\xpi.  Try two methods:
1) just "jre13i.exe" (will show UI)
2) "jre13i.exe -s -a -s" (will not show UI)

See if you get the same results as this bug.

ps. also 
1) what kinda of laptop do you have?

hp 4150

2) how much ram?

64 mb.

3) I see this bug is marked against Win95, but just to be sure, what OS are you 
running on it (any service packs too)?  If this is indeed Win95, can you run 
\\yatsura\bin$\w95debut.exe.  It will tell you if you have the first release of 
Win95 (the debute version) or not.

yes win95.  running \\yatsura\bin$\w95debut.exe.  pops a dialog
that shows "win95 debute NOT detected"

4) What's the longest time (that you can remember) waiting before killing the 
process?

A long time...  20+ minutes.
Putting on [nsbeta2-] radar.  Not critical to beta2.  Adding "relnote" keyword 
for PR2 release. 
Keywords: relnote
Whiteboard: [nsbeta2-]
When Java 2 Standard Edition (J2SE) v1.3 was packaged into the installer, all 
the jar files where crunched. Crunching is a mechanism to reduce the size of 
all the class files within the jar by merging all the strings in the class file 
constant pools. And the crunched jar files are bundled with the installer. 
During the J2SE installer, these jar files will be uncrunched into its original 
form. Therefore, additional disk space is needed by the installer to perform 
the uncrunching. However, we should make the installer smart enough to 
determine the lack of diskspace in the final release.
Status: NEW → ASSIGNED
Adding relnote2 keyword.
Keywords: relnote2
I'm fairly sure there is another relnoted bug about the installer hanging in low 
disk space situations...

Gerv
Whiteboard: [nsbeta2-] → [nsbeta2-] relnote-user
Keywords: freeze
Keywords: freezehang
Stanley, can we close this?
QA Contact: geetha.vaidyanaathan → avm
This is a RFE for the installer. Reassign it to Jim.
Assignee: stanley.ho → James.Melvin
Status: ASSIGNED → NEW
Closing this bug; it's not a Mozilla bug, but RFE for the Java Plug-In
installer.  Also adding keyword to the Status Whiteboard to distinguish this as
not a Mozilla bug.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → INVALID
Whiteboard: [nsbeta2-] relnote-user → [nsbeta2-] relnote-user jpibug
If this is invalid, then someone should take it out of the release notes for 0.9.9.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.