Closed Bug 173522 Opened 22 years ago Closed 20 years ago

need to reduce ENV variables in windows environment

Categories

(NSS :: Test, defect, P3)

Product:
NSS
Component:
Test
Platform:
x86
Windows 2000
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: sonja.mirtitsch, Assigned: bishakhabanerjee)

Details

bltest will run into segmentation violations on RSA Encrypt on Win2K running
Win95 OPT backward compatibility tests if too many environment variables are
being set.
Need to go through scripts and throw out unneeded variables.
See bug   Bug #173381 and bug #82393
When was this last seen?
Priority: -- → P3
not  seen since we switched to Windows 2000 professional from Windows 2000
Advanced Server.
Have not seen this lately, but would like to keep this bug open till another
occurance here at AOL, when I can test what worked for Sonja, that is reducing
env. variables. Will close it at that point if error goes away for that
particular build.
Setting target milestone to 3.9, if I don't see this happening by then, I will 
close this bug as "WORKSFORME"
Target Milestone: --- → 3.9
Sonja,

what env. variables did you remove from the QA scripts?

I see this same failure now on regular testing, while testing NSS344. 
I just went through the scripts and cleaned up. Maybe you can install a service
pack on the PC that will help?
I had installed all the service packs needed. No extra variables are present. 

Seen again today during testing for NSS 382 RTM, on elgamal (Win NT), not on
koblitz (Win XP). Seen on WIN 95 DBG bld in the Backward Compatibility Tests
section. Seen once.

Just a note for myself.
There is another bug open, Bug id=82393, which describes the same problem.

The problem described in this bug report (bltest will run into segmentation
violations on RSA Encrypt on Win2K running Win95 OPT backward compatibility
tests if too many environment variables are being set) is not happening due to
extra environment variables set. I have taken out all extraneous variables, and
we still occassionally see this crash (last crash seen was several months ago).

Hence, resolving this bug as WORKSFORME.

At the time this was last seen, it was discussed at an NSS metting, and the
consensus was that we needed more info about the crash. There is a new bug open
by Julien (bug id=221425) to see the pop-up dialog in case of a crash to get
more accurate information.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.