Closed Bug 964 Opened 26 years ago Closed 26 years ago

mozilla.exe - Application Error

Categories

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

x86
Windows NT

Tracking

(Not tracked)

VERIFIED WONTFIX

People

(Reporter: shawn.fisher, Assigned: blythe)

Details

This is in the nightly build test of mozilla. Version "%s - 5009808600" (Looks like something may be wrong there). I am using a Pentium Pro 200 with 64 Megs of ram (A micron system), my OS is NT 4.0 SP3 and IE4. I was trying to read the news at www.slashdot.org, and I recieved an Application Error. The contents of the box were : "The exception Breakpoint (Doah!) A breakpoint has been reached. (0x80000003)occurred in the application at location 0x77f76148. Click on OK to ... Click on CANCEL to ..." It appears as if someone left a breakpoint in the code, and needs to clear it... Also when I overlap mozilla onto another window, such as wordpad, then change focus to wordpad, I have a chunk of mozilla stuck on the wordpad window... And when I click on the "Email me a password" button without putting a name into the username section on the Bugzilla login screen, Mozilla asks if it wants me to remember the username and password, I click ok, and I get: "Debug Assertion Failed! Program: C:\Downloads.....\Mozilla.exe File: Y:\Nightly\Mozilla\cmd\winfe\fenet.cpp Line: 199 For information on how your program can cause an assertion failure .... (Press Retry...)" Hope this helps.
Severity: major → trivial
Severity: trivial → minor
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → WONTFIX
You won't get any ASSERTions if you run a non-debug/release build. The developer of the ASSERTion code must have some reason for having them there. I'm sorry that it wasn't a good experience.
Status: RESOLVED → VERIFIED
Component: Platform: MFC/Win32 on Windows → XPInstall
Old bug...marking Verified. .exe's are working with latest builds.
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.