More of a comment than a question or bug report. I would like to thank you guys for a nice job. Webkit browsing as you are defining it is a really nice change from normal browser use. That said, I worked with a developer for a short time, who is using the webkit browser in a project he's been working on for some time. I did some testing for him and the problem is that the webkit opens and closes within his app. No problem that it uses RAM during its use, but it carries over after its use. His app runs at about 40-60K RAM, but the webkit boosts it to 150-200k. This part is fine, but after the webkit is closed, the memory for his app stays at 150-200k. Worst of all, his app runs full-time, so the memory simply doesn't drop until a reboot. Any chance there will be a solution for memory management, so that the memory used by the webkit will drop out of an application once the webkit is closed? Sorry if this is something the developer should handle himself, but I am not a developer. It does seem like something that would be a good addition to the program. Please keep up the great work. Webkit browsers are the ultimate change of pace for people who use the internet a great deal...