Closed Bug 869294 Opened 12 years ago Closed 6 years ago

crash in XPCConvert::JSData2Native with abort message: "OOM: file e:\...\xpcom\string\src\nsTSubstring.cpp, line 291"

Categories

(Core :: XPConnect, defect)

Product:
Core
Component:
XPConnect
Version:
20 Branch
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED INACTIVE
Tracking Flags:
Tracking Status
firefox20 --- affected
firefox21 --- affected

People

(Reporter: morac, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is report bp-c7d3ff63-4fbf-40bd-ad26-725272130507 . ============================================================= A user is reporting that any time he installs my Session Manager add-on, that Firefox crashes with this signature within 10 minutes. I have no idea why since he's the only person who has reported this. As Session Manager is restartless, he tested by disabling it and starting Firefox which he claims ran fine. He then enabled Session Manager and Firefox crashed within 10 minutes. Session Manager does not do threading and I can't think of any reason why it would be doing nsXPCWrappedJS stuff. I did find the same crash signature for other users who don't have Session Manager installed.
I did notice this in his crash reports. I'm not sure if it's the crash cause or a result of the crash. Also I have no idea what it would have to do with Session Manager since it doesn't load dlls or use WebGL at all. D3D10 Layers? D3D10 Layers- D3D9 Layers? D3D9 Layers- WebGL? EGL? EGL+ GL Context? GL Context+ WebGL+ xpcom_runtime_abort(###!!! ABORT: OOM: file e:\builds\moz2_slave\rel-m-rel-w32_bld-000000000000\build\xpcom\string\src\nsTSubstring.cpp, line 291)
Yeah, looks like an out-of-memory crash. Can't say much more than that though.
Crash Signature: [@ mozalloc_abort(char const* const) | NS_DebugBreak_P | XPCConvert::JSData2Native(JSContext*, void*, JS::Value, nsXPTType const&, int, nsID const*, tag_nsresult*)] → [@ mozalloc_abort(char const* const) | NS_DebugBreak_P | XPCConvert::JSData2Native(JSContext*, void*, JS::Value, nsXPTType const&, int, nsID const*, tag_nsresult*) ]
status-firefox20: --- → affected
status-firefox21: --- → affected
OS: Windows NT → Windows XP
Summary: crash [@ mozalloc_abort(char const* const) | NS_DebugBreak_P | XPCConvert::JSData2Native(JSContext*, void*, JS::Value, nsXPTType const&, int, nsID const*, tag_nsresult*)] → crash in XPCConvert::JSData2Native with abort message: "OOM: file e:\...\xpcom\string\src\nsTSubstring.cpp, line 291"
This is what he told me: "I have 3GB of memory. I have a 4GB flash drive being used as Readyboast. I have session Manager set up to backup every 10 minutes. I do have a number of tabs open." An out of memory crash seems unlikely, but I guess it's possible. It would be nice if the crash log indicted how many windows/tabs were open, but I've seen people have thousands of tabs open without issue.
The crash report indicates how much memory is available. It looks like there is plenty. Memory corruption can manifest as an OOM.
Just for a sanity check on my end. Is there anything a JavaScript only add-on could do (other than do non-thread safe activities) that could cause this?
Crash Signature: [@ mozalloc_abort(char const* const) | NS_DebugBreak_P | XPCConvert::JSData2Native(JSContext*, void*, JS::Value, nsXPTType const&, int, nsID const*, tag_nsresult*) ] → [@ mozalloc_abort(char const* const) | NS_DebugBreak_P | XPCConvert::JSData2Native(JSContext*, void*, JS::Value, nsXPTType const&, int, nsID const*, tag_nsresult*) ] [@ mozalloc_abort | NS_DebugBreak_P | XPCConvert::JSData2Native ]
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.