| Summary: | [WK2][GTK] ASSERTION FAILED: m_touchEvents.contains(sequence) in some touch event tests | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Sergio Villar Senin <svillar> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | bugs-noreply, carlosg, cturner, hs85.jeong, mcatanzaro |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
|
Description
Sergio Villar Senin
2014-04-04 02:40:13 PDT
Adding Garnacho I'll have a look at that when I'm back from LGM Source/opensource/WebKitGTK/Source/WebKit2/UIProcess/API/gtk/WebKitWebViewBase.cpp (863)
uint32_t sequence = GPOINTER_TO_UINT(gdk_event_get_event_sequence(touchEvent));
If the touch event is GDK_TOUCH_BEGIN, gdk_event_get_event_sequence returns the value incrementally. (like as 1, 2, 3, 4...)
But if the touch event is GDK_TOUCH_END, gdk_event_get_event_sequence always returns the '1'.
STDERR: ASSERTION FAILED: m_touchEvents.contains(sequence)
At this time, sequence=1 already removed at first invoked webkitWebViewBaseTouchEvent().
So it makes the crash.
We have to investigate why gdk_event_get_event_sequence always return the '1' when touch event is GDK_TOUCH_END.
These crashes are no longer occurring, the tests just fail as before for reasons documented elsewhere. I believe r197351 stopped the assert firing. Please disregard previous comment, I still believe this is no longer crashing in debug builds from manual testing, but the automated tool that gave me the above commit on works off release logs, which I overlooked. Expectations updated in bug #173160. |