[Webkit-unassigned] [Bug 185762] New: [GTK] Initialize bmalloc only when needed

[bugzilla-daemon at webkit.org]

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

            Bug ID: 185762
           Summary: [GTK] Initialize bmalloc only when needed
           Product: WebKit
           Version: WebKit Local Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit Gtk
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: mcrha at redhat.com
                CC: bugs-noreply at webkitgtk.org

Would it be possible to initialize bmalloc only when it is really needed, please?

It's currently enough to preload WebKitGTK+ library and there's that bmalloc thread which has also some side effects, like the Gigacage allocations and so on. The Gigacage causes problems in various scenarios, when it crashes instead of fail gracefully and let the process run. (Like bug #183329 and downstream bug https://bugzilla.redhat.com/show_bug.cgi?id=1564970 ).

You can test it with such a simple program like this:

---------------------------------------

#include <stdio.h>
#include <stdlib.h>

int main (void)
{
        system ("sleep 30");
        return 0;
}

---------------------------------------

Compile it with:

   $ gcc simple.c -o simple -g

Then run it as:

   $ ./simple

and see its backtrace:

   $ gdb --batch --ex "t a a bt" -pid=`pidof simple`

which shows only a single thread and nothing else. Run it as this:

   $ LD_PRELOAD=/usr/lib64/libwebkit2gtk-4.0.so ./simple

and the backtrace will show also the bmalloc thread, even there's not called any single method from the webkit library.

-- 
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/20180518/f9fcd066/attachment-0001.html>