[Webkit-unassigned] [Bug 165656] [GTK] UIProcess from WebKitGtk+ 2.15.2 SIGSEGVs in WebKit::AcceleratedBackingStoreX11::update(WebKit::LayerTreeContext const&) () at Source/WebKit2/UIProcess/gtk/AcceleratedBackingStoreX11.cpp:145

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=165656

--- Comment #12 from Michael Catanzaro <mcatanzaro at igalia.com> ---
(In reply to comment #11)
> I've explained the steps to reproduce.

You've explained that it's not reproducible in any predictable way. I have no doubt that this is a problem and that I'll eventually start getting reports of it in Fedora; I guess we'll wait for those to come in to figure out what the X error is here....

(In reply to comment #11)
> -g1 is the difference between having an usable and debuggable ephy or not
> having it at all. These flags are not there by mistake but, actually by
> advice from you, developers.

Why do you have to use -g1? Unless you are building in an extremely memory-constrained environment, that should not be necessary.

(In reply to comment #11) 
> > bad idea to use G_DISABLE_CAST_CHECKS. That's going to make lots of bugs
> > much harder to solve, but that's not likely an issue here.)
> 
> Same than above.

I can't imagine that has a significant impact on performance...? Are you not able to use distro packages of WebKit at all, because they have cast checking enabled...? No distros use that and it's very much not supported as it changes critical warnings into mysterious crashes.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20161214/50052d29/attachment.html>