[Webkit-unassigned] [Bug 18361] New: Creating thread in web plugin breaks JavaScript timer functionality

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Apr 8 05:27:20 PDT 2008


           Summary: Creating thread in web plugin breaks JavaScript timer
           Product: WebKit
           Version: 525.x (Safari 3.1)
          Platform: Macintosh Intel
        OS/Version: Mac OS X 10.5
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebCore JavaScript
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: exittoshell at gmail.com

After creating a new thread in a WebKit plugin using [NSThread
detachNewThreadSelector: toTarget: withObject:] any existing or new JavaScript
timers created using setTimeout() fail to fire in the browser.

In a web plugin a thread is created in a Cocoa method that is exposed as a
JavaScript function using the JavaScript bridge feature. This Cocoa method is
called by a separate JavaScript function injected into the active DOM by the
web plugin.

Disabling the thread creation method in the plugin or disabling the plugin with
thread support and relaunching the browser enables JavaScript timers once more.

Example Plugin w/Threading that breaks JavaScript timers available upon

JavaScript timer tests:

Configure bugmail: http://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the webkit-unassigned mailing list