105894 2013-01-01 00:11:59 -0800 Objective-C API: Objective-C functions exposed to JavaScript stop working after JSContext is released 2013-02-21 17:47:02 -0800 1 1 1 Unclassified WebKit JavaScriptCore 528+ (Nightly build) Unspecified Unspecified RESOLVED FIXED InRadar P1 Normal --- 1 barraclough mhahnenberg ggaren mhahnenberg oldest_to_newest 798416 0 barraclough 2013-01-01 00:11:59 -0800 Instead we should probably retain a marked reference to the JSGlobalObject, and allocate a new JSContext as necessary. 814497 1 ddkilzer 2013-01-23 12:23:19 -0800 <rdar://problem/12954143> 839057 2 mhahnenberg 2013-02-21 17:24:11 -0800 I believe this was fixed in http://trac.webkit.org/changeset/143637. I'll try to write a test to verify this. 839085 3 mhahnenberg 2013-02-21 17:47:02 -0800 Actually we already get test coverage for this in the API tests from the aforementioned revision since they use setTimeout with Objective-C callbacks. I set a breakpoint in the code path that checks for null JSContexts in objCCallbackFunctionCallAsFunction and we hit it. So I think we can just close this bug.