Closed Bug 1489952 Opened 7 years ago Closed 3 years ago

Crash in js::InternalBarrierMethods<T>::readBarrier

Categories

(Core :: JavaScript: GC, defect, P5)

Unspecified
Android
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: gsvelto, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash, Whiteboard: qa-not-actionable)

Crash Data

This bug was filed from the Socorro interface and is report bp-e37826c4-a2b0-47f0-bac2-6ec4b0180910. ============================================================= Top 10 frames of crashing thread: 0 libxul.so js::InternalBarrierMethods<JSObject*>::readBarrier js/public/HeapAPI.h:169 1 libxul.so JSCompartment::getOrCreateWrapper js/public/Value.h:1374 2 libxul.so JSCompartment::wrap js/src/vm/JSCompartment.cpp:469 3 libxul.so mozilla::dom::GetPerInterfaceObjectHandle dom/bindings/BindingUtils.cpp:4077 4 libxul.so JS_WrapObject js/src/jsapi.cpp:783 5 libxul.so mozilla::dom::XrayGetNativeProto dom/bindings/BindingUtils.h:2534 6 libxul.so xpc::XrayWrapper<js::CrossCompartmentWrapper, xpc::DOMXrayTraits>::getPrototype 7 libxul.so wcsrtombs 8 libxul.so xpc::DOMXrayTraits::delete_ 9 libxul.so js::Proxy::get js/src/proxy/Proxy.cpp:195 =============================================================
Looking at the proto signatures, this is a fairly generic signature. It looks like there was a bit of a spike on Android Nightly (9, plus 3 on beta) of this signature, such as bp-7681ac5f-ac21-4549-a0f2-74d180180908 For those, the second frame is js::ArgumentsObject* js::ArgumentsObject::create<CopyFrameArgs>(JSContext*, JS::Handle<JSFunction*>, unsigned int, CopyFrameArgs&) and that's it.
Component: JavaScript Engine → JavaScript: GC

This is a low volume crash. The intermittent failure reports above are not related and are due to the problem fixed by bug 1480121.

Blocks: GCCrashes
Priority: -- → P5
Whiteboard: qa-not-actionable

Since the crash volume is low (less than 5 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.

For more information, please visit auto_nag documentation.

Severity: critical → S3

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.