I'm going to need rounding for large allocation sizes like jemalloc to work around poorly written applications and libraries with element-by-element realloc growth loops. GTK+ / Qt ecosystems are full of memory corruption & inefficient patterns like this.
github.com/AndroidHardeni
Conversation
It's all fine with server and command-line applications and on Android, but GTK+ and Qt applications often take a ridiculously long time to load because applications feel like reallocating 32 bytes to 32 MiB via realloc loops in increments of 32 bytes. Krita is particularly bad.
2
2
8
Epiphany does a lot of this but it's also packed full of memory corruption so it's hard to test performance... not that anyone should be using such an insecure browser anyway. Even Firefox's lack of meaningful sandboxing and other issues are way less bad than the WebKitGTK mess.
2
4
This Tweet was deleted by the Tweet author. Learn more
Replying to
It's still not good. They're moving towards eventually providing decent isolation separating content from the OS but it's not there yet. It also doesn't provide isolation between sites like Chromium's site isolation. See wiki.mozilla.org/Project_Fission for their site isolation project.
1
Replying to
It's certainly leagues ahead of WebKitGTK browsers like Epiphany but that's not saying a lot. Hardly anyone uses WebKitGTK browsers anyway because their rendering / compatibility is such trash so my complaints about it aren't particularly relevant to anyone. Still, it's a pain.
Replying to
I like to do broad application testing to make sure there aren't any compatibility issues and it's painful when those applications are full of latent memory corruption bugs and undefined behavior which I end up looking into since I need to waste time confirming each is their bug.