Bug 81382 - [Qt][WK2] Assertion failure on touch in touch webview
Summary: [Qt][WK2] Assertion failure on touch in touch webview
Status: RESOLVED DUPLICATE of bug 81144
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit2 (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-16 11:53 PDT by Dinu Jacob
Modified: 2012-03-16 12:58 PDT (History)
0 users

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 Dinu Jacob 2012-03-16 11:53:55 PDT 
Touch on any page results in an assertion failure:
ASSERTION FAILED: m_suspendCount
Source/WebKit2/UIProcess/qt/QtViewportInteractionEngine.cpp(380) : bool WebKit::QtViewportInteractionEngine::ensureContentWithinViewportBoundary(bool)


#0  0xb7c1914d in WebKit::QtViewportInteractionEngine::ensureContentWithinViewportBoundary (this=0x81040f0, 
    immediate=true) at Source/WebKit2/UIProcess/qt/QtViewportInteractionEngine.cpp:380
#1  0xb7c0aca3 in WebKit::QtPanGestureRecognizer::recognize (this=0x816cc38, event=0xbfffe2a8)
    at Source/WebKit2/UIProcess/qt/QtPanGestureRecognizer.cpp:69
#2  0xb7c0945b in QtWebPageEventHandler::doneWithTouchEvent (this=0x816cc28, event=..., wasEventHandled=false)
    at Source/WebKit2/UIProcess/qt/QtWebPageEventHandler.cpp:461
#3  0xb7c11863 in QtPageClient::doneWithTouchEvent (this=0x815cd4c, event=..., wasEventHandled=false)
    at Source/WebKit2/UIProcess/qt/QtPageClient.cpp:237
#4  0xb7bb602e in WebKit::WebPageProxy::handleTouchEvent (this=0x8173440, event=...)
    at Source/WebKit2/UIProcess/WebPageProxy.cpp:1043
#5  0xb7c08fbd in QtWebPageEventHandler::handleTouchEvent (this=0x816cc28, event=0xbfffe428)
    at Source/WebKit2/UIProcess/qt/QtWebPageEventHandler.cpp:357
#6  0xb7b385b5 in QQuickWebView::touchEvent (this=0x815cc08, event=0xbfffe428)
Comment 1 Dinu Jacob 2012-03-16 12:58:09 PDT 

*** This bug has been marked as a duplicate of bug 81144 ***