regxpcom.exe is crashing with the following error (and dialog). I was unable to get the screenshot of the dialog box, but here's what I have from the log. *SNIP* NMAKE : fatal error U1077: 'regxpcom.exe' : return code '0xc0000005' Stop. NMAKE : fatal error U1077: 'C:\PROGRA~1\MICROS~1\VC98\BIN\NMAKE.EXE' : return code '0x2' Stop. NMAKE : fatal error U1077: 'C:\PROGRA~1\MICROS~1\VC98\BIN\NMAKE.EXE' : return code '0x2' Stop. I am unable to get a mozilla trunk verification build out because of this.
confirming, i've been seeing this the last couple of days.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Are we still supporting nmake ?
Created attachment 79737 [details] [diff] [review] Fixes problem Don't hold references passed xpcom shutdown
Created attachment 79741 [details] [diff] [review] even better patch this has been checked into the trunk...
Attachment #79737 - Attachment is obsolete: true
note that this affects all platforms that use regxpcom to pre-generate a component registry (unix, windows), regardless of build system.
also missed 138090 which is not important
Comment on attachment 79741 [details] [diff] [review] even better patch this should probably go in for rc1
Attachment #79741 - Flags: approval+
fixed on trunk.... making critical since I want this to land for rc1.
Severity: blocker → critical
Checking in regxpcom.cpp; /cvsroot/mozilla/xpcom/tools/registry/regxpcom.cpp,v <-- regxpcom.cpp new revision: 18.104.22.168; previous revision: 22.214.171.124 done checked into branch.
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED
adding fixed1.0.0 keyword (branch resolution). This bug has comments saying it was fixed on the 1.0 branch and a bonsai checkin comment that agrees. To verify the bug has been fixed on the 1.0 branch please replace the fixed1.0.0 keyword with verified1.0.0.
You need to log in before you can comment on or make changes to this bug.