Closed Bug 849577 Opened 10 years ago Closed 9 years ago

Private build Firefox 19.0.2 startup crah 0xC0000005 with MOZ_PROFILE_GENERATE=1


(Core :: JavaScript Engine, defect)

19 Branch
Windows 7
Not set





(Reporter: s793016, Unassigned)


(Keywords: crash)

Crash Data

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120331 Firefox/10.0.2 SeaMonkey/2.7.2
Build ID: 20120401095132

Steps to reproduce:

Sorry, my English is very very poor.

Private build Firefox 19.0.2 startup crah with MOZ_PROFILE_GENERATE=1 + new profile.

Source Code : Firefox 19.0.2 without any patch.
Environment - all got the same problem:
1.i5-750 + 16GB ram + win 7 x64 sp1 + vs2010 sp1 ( main machine )
2.X2-250 + 2GB ram + XP SP3 + vs2010 sp1
3.virtualbox guest 2 cpu + 3GB ram + win 7 x32 sp1 + vs2010 sp1
4.xenserver guest 2 cpu + 3GB ram + win server 2008 + vs2010 sp1

Dump by vs2010 & binary with enable-debug can download from here:

== mozconfig ==
mk_add_options MOZ_MAKE_FLAGS="-j4" mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/../obj ac_add_options --disable-updater ac_add_options --disable-update-channel ac_add_options --disable-update-packaging ac_add_options --disable-maintenance-service ac_add_options --enable-crashreporter ac_add_options --enable-debug ac_add_options --disable-installer ac_add_options --enable-tests ac_add_options --enable-jemalloc ac_add_options --enable-optimize="-O2i -GL -GS-" # M$VC 2010 ac_add_options --enable-application=browser

== windows event log ==
The name of the log file: Application Source: Application Error Date: 2013/3/9 afternoon 11:51:43 Event ID: 1000 Category: (100) Level: error Keywords: traditional User: NA Computer: i5-750 Description: Faulting application name: firefox.exe, version:, time stamp: 0x513b4b90 The failed module name: unknown, version:, time stamp: 0x00000000 Exception code: 0xc0000005 Error displacement: 0x004006f2 Failure handler ID: 0x2068 Faulting application start time: 0x01ce1cdd33ea4c76 The failed application path: d: \ mozilla \ obj \ dist \ bin \ firefox.exe Failed module path: unknown Report ID: 3c9ae912-88d1-11e2-813b-ff6189ea1304 Event Xml: <Event Xmlns="">

   <Provider Name="Application Error" />
   <EventID Qualifiers="0"> 1000 
   <Level> 2 
   <Task> 100 
   <Keywords> 0x80000000000000 
   <TimeCreated SystemTime="2013-03-09T15:51:43.000000000Z" />
   <EventRecordID> 26641 
   <Channel> Application 
   <Computer> I5-750 
   <Security />
   <Data> Firefox.exe 
   <Data> 513b4b90 
   <Data> Unknown 
   <Data> 00000000 
   <Data> C0000005 
   <Data> 004006f2 
   <Data> 2068 
   <Data> 01ce1cdd33ea4c76 
   <Data> D: \ mozilla \ obj \ dist \ bin \ firefox.exe 
   <Data> Unknown 
   <Data> 3c9ae912-88d1-11e2-813b-ff6189ea1304 

== vs2010 debug show "AvailableMemoryTracker.cpp" ==
// It's tempting to see whether we have enough free virtual address space for
 // this allocation and, if we don't, synchronously fire a low-memory
 // notification to free some before we allocate.
 // Unfortunately that doesn't work, principally because code doesn't expect a
 // call to malloc could trigger a GC (or call into the other routines which
 // are triggered by a low-memory notification).
 // I think the best we can do here is try to allocate the memory and check
 // afterwards how much free virtual address space we have.  If we're running
 // low, we schedule a low-memory notification to run as soon as possible.

here -=-=> LPVOID result = sVirtualAllocOrig(aAddress, aSize, aAllocationType, aProtect);

 // Don't call CheckMemAvailable for MEM_RESERVE if we're not tracking low
 // virtual memory.  Similarly, don't call CheckMemAvailable for MEM_COMMIT if
 // we're not tracking low physical memory.
 if ((sLowVirtualMemoryThreshold != 0 && aAllocationType & MEM_RESERVE) ||
     (sLowPhysicalMemoryThreshold != 0 && aAllocationType & MEM_COMMIT)) {
   LOG3("VirtualAllocHook(size=", aSize, ")");

Actual results:

startup crash error code 0xC0000005 

Expected results:

no crash.
Severity: normal → critical
Keywords: crash
Do you have a crash ID in about:crashes?
Assignee: nobody → general
Crash Signature: [@ JSD_ClearAllProfileData(JSDContext*) ]
Component: Untriaged → JavaScript Engine
Flags: needinfo?(s793016)
Product: Firefox → Core
I am sorry there is no crash report inside "%APPDATA%\Mozilla\Firefox\Crash Reports".

The profile folder only got 2 files inside:
1.parent.lock (size 0 byte)
2.compatibility.ini - below is file contents.
Flags: needinfo?(s793016)
Closed: 9 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 670967
You need to log in before you can comment on or make changes to this bug.