Why is the latest WebKit interacting with my NSThread? [WebKit Threading Violation]

  • Greetings,
    Since upgrading to 10.4.11 and Safari 3, I notice now that a thread in my
    application throws the following errors when an NSThread thread runs:

    WebKit Threading Violation - +[DOMDocument(WebCoreInternal) _wrapDocument:]
    called from secondary thread

    WebKit Threading Violation - +[DOMCSSStyleDeclaration(WebCoreInternal)
    _wrapCSSStyleDeclaration:] called from secondary thread

    WebKit Threading Violation - -[DOMCSSValue dealloc] called from secondary
    thread

    WebKit Threading Violation - -[DOMNode dealloc] called from secondary thread

    Yes, my application does use WebKit, but this thread is a background thread,
    shouldn't be interacting with the main event thread, and certainly has
    nothing to do with WebKit, it has no knowledge of it at all (though it is
    using [[NSXMLDocument alloc] initWithContentsOfURL:url
    options:NSXMLDocumentTidyXML error:&error] within it), yet for some reason
    there seems to be an interaction while running. Is it because of the
    NSXMLDocument? I can't imagine calling it in a thread should be a problem
    now. I'm essentially fetching and processing an XMLDoc in this thread.

    Is there something that changed from Safari 2 to 3 that I need to be aware
    of? Maybe this is more appropriate for another list, but I'm not really
    doing anything special with WebKit, and I'm just using everything straight
    from Cocoa, I'm not downloading and doing my own builds, etc, so I think
    this question is appropriate here. Any clue of pointers to info on how to
    change things would be appreciated (I looked but couldn't really find
    anything).

    Thanks,

    Michael
previous month december 2007 next month
MTWTFSS
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
31            
Go to today