Using bugzilla-tool

Bugzilla-tool is a useful tool for managing bugzilla related activities. You can do many things with it, e.g., create bugreports from local trunk and apply patches to local trunk, land patches automatically. The only thing that you have to use is your command line... The tool is located in the WebKitTools/Scripts directory, but it has some requirements.

Progress of the Code Camp

So, it seems that everyone survived the first day (and the night...) For those who are not here with us in Wiesbaden but are interested, here is a link where the progress of the camp can be followed. (Provided that people are not too lazy to upload content... :) )

QtWebKit Code Camp started

Half of our team is now in Wiesbaden, Germany. We will stay here for 3 days and participate on the QtWebKit Code Camp. Quite a big bunch of people gathered here - more than 50 people from 3 continents (or more). It's great to have so many nicks here from #qtwebkit. And look, the nicks have faces! :)

Detailed memory consumption of some popular sites. Poor good old malloc, everyone's beast of burden.

It is time to try out my new freya tool. Only some web-sites and a fresh Qt (4.6.0) and QtWebKit (r51481) are needed. The values are peak memory consumptions, which is not necessary the best choice (since the sum of their total value is greater than the peak memory consumption), but at least we can see the memory hungry parts of QtWebKit.

A new tool to extract meaningful memory consumption values. Valgrind shines again.

Every program allocates memory, regardless of its size. Reducing it is an important task and an eternal struggle. Using advanced memory profiling tools, it is easy to see that the most memory is consumed by ... hash tables, vectors, unicode strings, mmaped memory regions, etc. But is THIS what you are interested in? Isn't it would be better to know how much memory consumed by WebCore, JavaScriptCore, Qt, or by a particular component, like WebCore/css?

Boost ARM-JIT engine with Nitro Extreme. Brace for impact.

There was a post about Nitro Extreme some time ago on this site, so it is time to recollect what happened so far. Nitro Extreme is not a branch anyomore, it went to mainline, and replaced the old JavaScript Value (JSValue) representation on 32 bit machines. To be more precise, it happened only on x86.

Compiling WebKitGTK+ on Scratchbox for ARM platform

If we would like to build WebKitGTK+ for ARM platform, Scratchbox could be a good choice. In this post I will show, how we can install and setup Scratchbox to build WebKitGTK+. First, we have to install the Scratchbox and its ARM target. Next, we install some libraries to WebKitGTK+.
Let's see how we can do that.

The effect of TCmalloc in the QtWebKit port - stage 2: Memory consumption

As I mentioned, there is a reverse of a medal, so now let's see how enabling TCmalloc on the QtWebKit port's JavaScriptCore engine effects memory consumption.

Building QtWebKit on Windows

When I tried to build QtWebKit on Windows the first time, I realized it was a more complex task than on Linux. I experimented a lot to make building, testing and WebKit scripts work correctly. I decided that I would fix imperfect scripts and write a blogpost about this topic to relieve WebKit developers sufferings.

The effect of TCmalloc in the QtWebKit port - stage 1: Performance

Much time has passed since we started to work on the custom allocation framework with Paul Pedriana. The core of the solution (FastAllocBase class, bug #20422) was landed into the trunk half year ago.