Closed Bug 1103939 Opened 10 years ago Closed 10 years ago

getting "Udump" Pointing to "APPLICATION_FAULT_STATUS_BREAKPOINT_mozalloc!mozalloc_abort+2a

Categories

(Firefox :: Untriaged, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: pinky.rizwani, Unassigned, NeedInfo)

Details

User Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; InfoPath.3) Steps to reproduce: Tried Opeining the Firefox through an Automated Test Suit Actual results: Got Udump poiting to the crash mentioned above. Expected results: No any Crash is expected.
BREAKPOINT crashes are often for harmless reasons (failure to allocate memory is most common). In order to decide whether this is a bug, we need the full Firefox stack of the crash. Please see https://developer.mozilla.org/en-US/docs/How_to_get_a_stacktrace_for_a_bug_report for instructions.
Flags: needinfo?(pinky.rizwani)
The general reason for the mozalloc_abort call is a failure to allocate the requested memory -- that is you're out of memory (or close to it with a big request) -- where Firefox aborts rather than risk continuing in an unstable state. Been a couple of weeks, we're unlikely to get the requested info at this point.
Group: core-security
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.