Large OOM in std::_Allocate, coming from JSStreamWriter

RESOLVED WORKSFORME

Status

()

--
critical
RESOLVED WORKSFORME
4 years ago
2 years ago

People

(Reporter: alex_mayorga, Unassigned)

Tracking

({crash})

32 Branch
x86
Windows 7
crash
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(crash signature)

(Reporter)

Description

4 years ago
This bug was filed from the Socorro interface and is 
report bp-9a5425cf-986b-43d7-99f4-fa3c22140820.
=============================================================

Comment 1

4 years ago
Relevant stack snippet:

3 	xul.dll 	std::_Allocate<char>(unsigned int, char*) 	c:/program files (x86)/microsoft visual studio 10.0/vc/include/xmemory:36
4 	xul.dll 	std::allocator<char>::allocate(unsigned int) 	c:/program files (x86)/microsoft visual studio 10.0/vc/include/xmemory:187
5 	xul.dll 	std::basic_stringbuf<char, std::char_traits<char>, std::allocator<char> >::overflow(int) 	c:/program files (x86)/microsoft visual studio 10.0/vc/include/sstream:150
6 	msvcp100.dll 	std::basic_streambuf<char, std::char_traits<char> >::sputc(char) 	f:\dd\vctools\crt_bld\self_x86\crt\src\streambuf:196
7 	xul.dll 	std::operator<<<std::char_traits<char> >(std::basic_ostream<char, std::char_traits<char> >&, char) 	c:/program files (x86)/microsoft visual studio 10.0/vc/include/ostream:833
8 	xul.dll 	EscapeToStream 	tools/profiler/JSStreamWriter.cpp
9 	xul.dll 	JSStreamWriter::Name(char const*) 	tools/profiler/JSStreamWriter.cpp
10 	xul.dll 	ThreadProfile::StreamJSObject(JSStreamWriter&) 	tools/profiler/ProfileEntry.cpp
Component: General → Gecko Profiler
Product: Firefox → Core
Summary: crash in OOM | large | mozalloc_abort(char const* const) | mozalloc_handle_oom(unsigned int) | moz_xmalloc | std::_Allocate<char>(unsigned int, char*) → Large OOM in std::_Allocate, coming from JSStreamWriter
I have gotten a couple of these in the recent nightly. I did not get any of these before E10S was enabled so it could be related to that.

https://crash-stats.mozilla.com/report/index/f28b6dca-cc9d-4483-94c2-a8ee82141108
https://crash-stats.mozilla.com/report/index/34871e46-3a6d-42da-93f7-4c8d82141107

No reproducible steps identified so far.
(In reply to Ryan Jones from comment #2)
> I have gotten a couple of these in the recent nightly. I did not get any of
> these before E10S was enabled so it could be related to that.
> 
> https://crash-stats.mozilla.com/report/index/f28b6dca-cc9d-4483-94c2-
> a8ee82141108
> https://crash-stats.mozilla.com/report/index/34871e46-3a6d-42da-93f7-
> 4c8d82141107
> 
> No reproducible steps identified so far.

This may or may not be the same bug, if not then it will likely need to be split off. This was suggested by the crash reporting system though.

Updated

3 years ago
Crash Signature: [@ OOM | large | mozalloc_abort(char const* const) | mozalloc_handle_oom(unsigned int) | moz_xmalloc | std::_Allocate<char>(unsigned int, char*)] → [@ OOM | large | mozalloc_abort(char const* const) | mozalloc_handle_oom(unsigned int) | moz_xmalloc | std::_Allocate<char>(unsigned int, char*)] [@ OOM | large | mozalloc_abort | mozalloc_handle_oom | moz_xmalloc | std::_Allocate<T>]
(Reporter)

Comment 4

2 years ago
No crashes for either signature in the past week, resolving.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.