Bug 134685 - Should -[WebGLLayer display] call WebThreadLock?
Summary: Should -[WebGLLayer display] call WebThreadLock?
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebGL (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-07 10:53 PDT by Simon Fraser (smfr)
Modified: 2023-04-21 01:01 PDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Fraser (smfr) 2014-07-07 10:53:11 PDT 
WebLayer's -display looks like:

- (void)display
{
#if PLATFORM(IOS)
    if (pthread_main_np())
        WebThreadLock();
#endif

and this is necessary since this as a place where CA calls back into WebKit.

This lock is missing in the WebGL -display implementation.