[Webkit-unassigned] [Bug 179914] [GTK] Crash in IsoAllocator::allocateSlow (WTF::Signal::BadAccess)

[bugzilla-daemon at webkit.org]

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

--- Comment #42 from Saam Barati <sbarati at apple.com> ---
(In reply to Michael Catanzaro from comment #41)
> (In reply to Milan Crha from comment #39)
> > I'm not able to run WebKitWebProcess under valgrind, it crashes with:
> 
> That's not going to work unless Gigacage is disabled. I don't know if it's
> possible to disable Gigacage at runtime. Disabling bmalloc (using
> https://trac.webkit.org/wiki/EnvironmentVariables) should suffice, but then
> you can't test the crash we're investigating....

It’s easy to do at runtime. Look at Gigacage.cpp, inside bmalloc. It reads an environment variable when determining if Gigacage is enabled

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20171207/9634afa5/attachment.html>