UniscribeHelper::draw() should not ASSERT that ScriptTextOut() always succeed. It even has logic to deal with this kind of failures.
Created attachment 53302 [details]
For background, we probably used to have a DCHECK here with is a debug-only assert to help catch errors. However, there are legitimate reasons this function may fail, especially in the Chrome sandbox, which is what the existing recovery code is supposed to do.
Comment on attachment 53302 [details]
Landed as r57595.
has been failing consistently on SnowLeopard since this checkin:
ASSERTION FAILED: m_wrapper || !m_jsFunction
(/Volumes/Data/WebKit-BuildSlave/snowleopard-intel-leaks/build/WebCore/bindings/js/JSEventListener.h:83 JSC::JSObject* WebCore::JSEventListener::jsFunction(WebCore::ScriptExecutionContext*) const)
That's the same ASSERT as bug 36779, except now its failing every time.
Nevermind, this test is flakey and has been failing for much longer.