Bug 153302 - [GTK] WebProcess from WebKitGtk+ 2.10.5 SIGUSR2 upon visiting http://maps.google.com
Summary: [GTK] WebProcess from WebKitGtk+ 2.10.5 SIGUSR2 upon visiting http://maps.goo...
Status: RESOLVED DUPLICATE of bug 153194
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: WebKit Local Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-21 02:00 PST by Andres Gomez Garcia
Modified: 2016-01-21 06:33 PST (History)
5 users (show)

See Also:

Attachments
BT from gdb (45.39 KB, text/plain)
2016-01-21 02:00 PST, Andres Gomez Garcia 		no flags Details
Another BT from gdb (37.97 KB, text/plain)
2016-01-21 02:01 PST, Andres Gomez Garcia 		no flags Details
View All 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 Andres Gomez Garcia 2016-01-21 02:00:47 PST 
Created attachment 269440 [details]
BT from gdb

I'm using WebKitGtk+ with my own JHBuild setting:
https://github.com/tanty/jhbuild-epiphany/tree/master

Epiphany 3.18.0 and WebKit 2.10.5

I'm running Epiphany with the dconf key:

"process-model" = "shared-secondary-process"

The compilation was done with CMake args:

'-DPORT=GTK -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS_RELEASE="-O0 -g1 -DNDEBUG -DG_DISABLE_CAST_CHECKS" -DCMAKE_CXX_FLAGS_RELEASE="-O0 -g1 -DNDEBUG -DG_DISABLE_CAST_CHECKS"'

When going to http://maps.google.com, the tab gets stalled at around 90% loaded. WebKitWebProcess receives a SIGUSR2. When continuing, the tab never gets to the 100% load, it is unresponsive and no new tabs or old open ones work any more. Fortunately, it is possible to safely close the browser and restore the session.

The SIGUSR2 is received in different points of the code under different executions.

This bug is 100% reproducible.
Comment 1 Andres Gomez Garcia 2016-01-21 02:01:15 PST 
Created attachment 269441 [details]
Another BT from gdb
Comment 2 Zan Dobersek 2016-01-21 02:33:53 PST 
Perhaps related to bug #153194.
Comment 3 Andres Gomez Garcia 2016-01-21 04:42:41 PST 
(In reply to comment #2)
> Perhaps related to bug #153194.

Yes, looks like the same bug.
Comment 4 Andres Gomez Garcia 2016-01-21 04:43:17 PST 
BTW, I didn't perceived this with 2.10.4
Comment 5 Carlos Garcia Campos 2016-01-21 05:48:31 PST 
Ok, this limits the amount of commits to blame then, it's something landed in trunk between 2.11.1 and 2.11.3 and merged in 2.10.5 (there are 155 commits merged in 2.10.5, though)
Comment 6 Michael Catanzaro 2016-01-21 06:33:50 PST 

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