Bug 1554873

Summary: FeedReader crashes after clicking a link in webview
Product: [Fedora] Fedora Reporter: Jiri Eischmann <jeischma>
Component: webkit2gtk3Assignee: Tomas Popela <tpopela>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 28CC: jbicha, mcatanzaro, tpopela
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-13 16:24:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jiri Eischmann 2018-03-13 13:47:13 UTC
FeedReader crashes every time I try to click a link in the webview and it seems like a bug in WebKit. See the backtrace:

#0  0x00007fdbc1fb08d8 in void std::call_once<Gigacage::ensureGigacage()::{lambda()#1}>(std::once_flag&, Gigacage::ensureGigacage()::{lambda()#1}&&)::{lambda()#2}::_FUN() ()
    at /lib64/libjavascriptcoregtk-4.0.so.18
#1  0x00007fdbc6ea2e87 in __pthread_once_slow () at /lib64/libpthread.so.0
#2  0x00007fdbc1fb0291 in Gigacage::ensureGigacage() () at /lib64/libjavascriptcoregtk-4.0.so.18
#3  0x00007fdbc1fb10ec in bmalloc::Heap::Heap(bmalloc::HeapKind, std::lock_guard<bmalloc::StaticMutex>&) () at /lib64/libjavascriptcoregtk-4.0.so.18
#4  0x00007fdbc1faeeba in bmalloc::PerProcess<bmalloc::PerHeapKind<bmalloc::Heap> >::getSlowCase() () at /lib64/libjavascriptcoregtk-4.0.so.18
#5  0x00007fdbc1faeb49 in bmalloc::Cache::Cache(bmalloc::HeapKind) () at /lib64/libjavascriptcoregtk-4.0.so.18
#6  0x00007fdbc1faef88 in bmalloc::PerThread<bmalloc::PerHeapKind<bmalloc::Cache> >::getSlowCase() () at /lib64/libjavascriptcoregtk-4.0.so.18
#7  0x00007fdbc1faebc3 in bmalloc::Cache::allocateSlowCaseNullCache(bmalloc::HeapKind, unsigned long) () at /lib64/libjavascriptcoregtk-4.0.so.18
#8  0x00007fdbc1f939ea in WTF::StringImpl::createFromLiteral(char const*, unsigned int) () at /lib64/libjavascriptcoregtk-4.0.so.18
#9  0x00007fdbc1f93a75 in WTF::StringImpl::createFromLiteral(char const*) () at /lib64/libjavascriptcoregtk-4.0.so.18
#10 0x00007fdbc1fa0134 in WTF::String::String(WTF::ASCIILiteral) () at /lib64/libjavascriptcoregtk-4.0.so.18
#11 0x00007fdbc27b440b in _GLOBAL__sub_I_PasteboardHelper.cpp () at /lib64/libwebkit2gtk-4.0.so.37
#12 0x00007fdbc7c1c6ba in call_init.part () at /lib64/ld-linux-x86-64.so.2
#13 0x00007fdbc7c1c7b6 in _dl_init () at /lib64/ld-linux-x86-64.so.2
#14 0x00007fdbc7c0df9a in _dl_start_user () at /lib64/ld-linux-x86-64.so.2
#15 0x0000000000000001 in  ()
#16 0x00007ffd68a401eb in  ()
#17 0x0000000000000000 in  ()

It crashes both with webkit2gtk3 2.19.91 (currently in F28 repos) and 2.20 (currently built in Koji). The version of FeedReader is 2.0.2.

Comment 1 Michael Catanzaro 2018-03-13 16:24:32 UTC
If you're able to participate in the upstream bug, that would be great, because we need help debugging this.

Comment 2 Jeremy Bicha 2018-03-13 16:35:52 UTC
Jiri, can you still reproduce your particular issue after upgrading mutter to 3.28.0 and restarting your computer?

Comment 3 Michael Catanzaro 2018-03-13 16:38:56 UTC
(In reply to Jeremy Bicha from comment #2)
> Jiri, can you still reproduce your particular issue after upgrading mutter
> to 3.28.0 and restarting your computer?

You're thinking of https://gitlab.gnome.org/GNOME/mutter/issues/63, which is surely different. I'd be astounded if mutter was at fault for this.

Comment 4 Tomas Popela 2018-03-14 07:39:57 UTC
(In reply to Michael Catanzaro from comment #1)
> If you're able to participate in the upstream bug, that would be great,
> because we need help debugging this.

I will prepare a scratch build for Jiri with the debug code from the upstream bug.

Comment 5 Tomas Popela 2018-03-14 09:42:05 UTC
(In reply to Tomas Popela from comment #4)
> (In reply to Michael Catanzaro from comment #1)
> > If you're able to participate in the upstream bug, that would be great,
> > because we need help debugging this.
> 
> I will prepare a scratch build for Jiri with the debug code from the
> upstream bug.

https://koji.fedoraproject.org/koji/taskinfo?taskID=25693641

Comment 6 Jiri Eischmann 2018-03-14 12:37:55 UTC
(In reply to Michael Catanzaro from comment #3)
> (In reply to Jeremy Bicha from comment #2)
> > Jiri, can you still reproduce your particular issue after upgrading mutter
> > to 3.28.0 and restarting your computer?
> 
> You're thinking of https://gitlab.gnome.org/GNOME/mutter/issues/63, which is
> surely different. I'd be astounded if mutter was at fault for this.

It was indeed this problem. After updating mutter to 3.28.0, the FeedReader can open links again.

Comment 7 Michael Catanzaro 2018-03-14 13:56:26 UTC
(In reply to Jiri Eischmann from comment #6)
> It was indeed this problem. After updating mutter to 3.28.0, the FeedReader
> can open links again.

I don't think a mutter update could have an effect on a crash in ensureGigacage. Are you sure the backtrace you posted is really related...?

Comment 8 Jiri Eischmann 2018-03-14 14:34:24 UTC
(In reply to Michael Catanzaro from comment #7)
> (In reply to Jiri Eischmann from comment #6)
> > It was indeed this problem. After updating mutter to 3.28.0, the FeedReader
> > can open links again.
> 
> I don't think a mutter update could have an effect on a crash in
> ensureGigacage. Are you sure the backtrace you posted is really related...?

I'm pretty sure it was from that crash. Tomas was with me when I looked up the backtrace, so he can testify it.
I haven't updated webkit2gtk3, just mutter and I've been using FeedReader for some time and haven't been able to reproduce the crash at all.