Summary: Memory leak with many layers open
Creator:commodorejohn Date:2008-04-02 12:36:08
Project:K-Meleon Owner:.Nobody
Status:Fixed Severity:Normal
Version:1.1.4 Target Version:1.5b1

User-agent: Firefox/1.0.7

When browsing deviantArt on K-Meleon, I have found that it does not deallocate the memory for pages that I close. Try this:

* Go to any deviantArt gallery.
* Open a number of image pages in separate tabs.
* View the K-Meleon process in Task Manager, and note how much memory is used.
* Close the image pages, but leave K-Meleon open.
* View the process in Task Manager again - it should have about the same amount of memory allocated, despite the fact that the pages have been closed.

The memory is deallocated when K-Meleon itself is closed, but not when the tabs are closed, meaning that the longer a session is open the slower and more crash-prone it becomes. I've replicated the problem on other sites (specifically, the Houston Chronicle comics page -,) but it doesn't happen to as severe an extent.

kko  2008-04-21 06:07:29
K-Meleon 1.1.x is using layers, not tabs. Since the layers are anyway going to be replaced by true tabs in K-Meleon 1.5, I've tested with 1.5b1 and compared to SeaMonkey 1.1.9.

The results are comparable. After opening a dozen of tabs, memory usage increases first over some minutes of inactivity, then stabilizes. When tabs are closed, memory is freed.

The only noticable difference between K-Meleon 1.5 and SeaMonkey 1.1 is that K-Meleon is genarally using less memory and is automatically freeing unnecessary memory when it is minimized.

- Can't reproduce in 1.5.
- If there is really such a problem in 1.1, it seems to be fixed in 1.5.

I don't doubt the report, so I mark this as fixed.

[Changed Status from "Unconfirmed" to "Fixed"]
[Changed Target from "Unknow" to "1.5b1"]
[Changed Summary from "Memory leak with many tabs open" to "Memory leak with many layers open"]

SourceForge Logo