Closed Bug 608963 Opened 15 years ago Closed 15 years ago

"ASSERTION: bad this object in get" crash [@ xpc::holder_get ]

Categories

(Core :: XPConnect, defect)

x86
macOS
defect
Not set
critical

Tracking

()

RESOLVED FIXED
Tracking Status
blocking2.0 --- beta7+

People

(Reporter: jruderman, Assigned: mrbkap)

Details

(Keywords: assertion, regression, testcase)

Attachments

(3 files)

###!!! ASSERTION: bad this object in get: 'wrapper->isProxy()', file js/src/xpconnect/wrappers/XrayWrapper.cpp, line 158 Assertion failure: isProxy(), at jsproxy.h:188 This is a regression from mrbkap's landings last night.
Attached file stack traces
Attached patch FixSplinter Review
ray wrappers don't really support arbitrary getters and setters, so delegating to one should not pass the original object through, but instead use the wrapper. This is congruous to the while loop in XPC_NW_GetOrSetProperty in the olden days.
Assignee: nobody → mrbkap
Status: NEW → ASSIGNED
Attachment #487634 - Flags: review?(gal)
Comment on attachment 487634 [details] [diff] [review] Fix Weird. This is pretty hacky.
Attachment #487634 - Flags: review?(gal) → review+
Does b7 need this or is b8 good enough?
blocking2.0: --- → ?
Given that this actually crashes in opt builds (and it's a regression from yesterday), b7 would be nice. But I don't think this is going to hit on any real sites or extensions, so b8 would be OK too.
Blocking beta7, but if this was the last and only bug and we didn't have a patch I'd punt. So land this ASAP :)
blocking2.0: ? → beta7+
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Summary: "ASSERTION: bad this object in get" → "ASSERTION: bad this object in get" crash [@ xpc::holder_get ]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: