Closed Bug 502449 Opened 16 years ago Closed 16 years ago

Crash [@ __memcpy]

Categories

(Core :: JavaScript Engine, defect)

x86
macOS
defect
Not set
critical

Tracking

()

RESOLVED FIXED
Tracking Status
status1.9.2 --- beta1-fixed
status1.9.1 --- .2-fixed

People

(Reporter: gkw, Assigned: mrbkap)

References

Details

(Keywords: crash, regression, testcase, Whiteboard: fixed-in-tracemonkey)

Crash Data

Attachments

(1 file)

(function() { x = this.watch("x", function() { function x() { return * ::* } }) })() crashes js opt and debug shell from TM branch without -j at __memcpy. Haven't yet tested on 1.9.1, and won't have time to autoBisect yet for a couple of days. === Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000 Crashed Thread: 0 Thread 0 Crashed: 0 libSystem.B.dylib 0xffff07c2 __memcpy + 34 (cpu_capabilities.h:246) 1 js-opt-tm-intelmac 0x00042137 js_PutCallObject + 327 2 js-opt-tm-intelmac 0x00024170 js_watch_set + 736 3 js-opt-tm-intelmac 0x00068ff3 js_NativeSet + 227 4 js-opt-tm-intelmac 0x00069950 js_SetPropertyHelper + 1616 5 js-opt-tm-intelmac 0x0004a3f5 js_Interpret + 2853 6 js-opt-tm-intelmac 0x000598f9 js_Execute + 409 7 js-opt-tm-intelmac 0x0000e88c JS_ExecuteScript + 60 8 js-opt-tm-intelmac 0x000043e0 Process(JSContext*, JSObject*, char*, int) + 1616 9 js-opt-tm-intelmac 0x00007aaf main + 879 10 js-opt-tm-intelmac 0x000025bb _start + 209 11 js-opt-tm-intelmac 0x000024e9 start + 41
Flags: blocking1.9.2?
Attached patch FixSplinter Review
Assignee: general → mrbkap
Status: NEW → ASSIGNED
Attachment #386891 - Flags: review?(igor)
Attachment #386891 - Flags: review?(brendan)
This is fallout from bug 501270. It did not affect the 1.9.0 version of the patch from that bug because igor's call object optimization didn't land on that branch.
Attachment #386891 - Flags: review?(igor) → review+
Comment on attachment 386891 [details] [diff] [review] Fix Gonna go with Igor's r+ here. /be
Attachment #386891 - Flags: review?(brendan)
This bug doesn't seem to affect 1.9.1.
Keywords: regression
Flags: blocking1.9.2? → blocking1.9.2+
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment on attachment 386891 [details] [diff] [review] Fix Needed if we take bug 501270 on the 1.9.1 branch.
Attachment #386891 - Flags: approval1.9.1.2?
Comment on attachment 386891 [details] [diff] [review] Fix Approved for 1.9.1.2. a=ss for release-drivers Please land on mozilla-1.9.1 and use the ".2-fixed" option of the "status1.9.1" flag.
Attachment #386891 - Flags: approval1.9.1.2? → approval1.9.1.2+
test passes in 1.9.1 shell on mac, but never failed there.
What is the best/simplest way for QA to verify this on 3.5.2?
Flags: in-testsuite?
Mass change: adding fixed1.9.2 keyword (This bug was identified as a mozilla1.9.2 blocker which was fixed before the mozilla-1.9.2 repository was branched (August 13th, 2009) as per this query: http://is.gd/2ydcb - if this bug is not actually fixed on mozilla1.9.2, please remove the keyword. Apologies for the bugspam)
Keywords: fixed1.9.2
Flags: wanted1.9.0.x-
Crash Signature: [@ __memcpy]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: