Closed Bug 8456 Opened 25 years ago Closed 25 years ago

Triggering jar files crashes intermittantly

Categories

(Core Graveyard :: Installer: XPInstall Engine, defect, P2)

All
Windows NT

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: jimmykenlee, Assigned: dveditz)

Details

Build: 6/17/99 SeaMonkey build 1. Use trigger http://puma/xpinstall/test/trigger.html (Samir's kinder, gentler trigger. 2. Trigger http://jimbob/jars/a_execute_parameter.jar RESULT: Crash. You may have to trigger the jar more than once within the same session. This is intermittant, but I've captured a Talkback stack trace (Incident ID = TB10118389Q). Call Stack: (Signature = 0x0012fe80 0de9cdab) 0x0012fe80 The Install.log shows that the installscript did not complete. --------------------------------------------------------------------------- Acceptance: a_execute_parameter --------------------------------------------------------------------------- Starting Installation at 06/17/1999 15:53:29 Item [1/1] Executing: C:\TEMP\xpinstall-3.exe EXPECTED RESULT: No crash. Install.log shows that installscipt completes successfully. Notepad.exe launches.
Target Milestone: M9
Severity: critical → major
Priority: P3 → P2
adjusting priority
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
I tried 10 times in a row without a crash using the steps given.
Status: RESOLVED → VERIFIED
Marking Verified. There definitely is still a crasher somewhere. I think I have a reproducible case. I write this up in a new report since it's different from this one.
Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall Engine
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.