Hi, can you determine whether this still occurs when running Midori with "midori --plain"? This tests the WebKit rendering engine alone, so we can tell whether this is caused by code in Midori itself having leaks, or if WebKit is leaky (or both).
Hi, can you determine whether this still occurs when running Midori with "midori --plain"? This tests the WebKit rendering engine alone, so we can tell whether this is caused by code in Midori itself having leaks, or if WebKit is leaky (or both).