After extensive testing and confirmation from Apple employees we realized that there was no way for an allocator to give unused pages of memory back while keeping the address range reserved. Mac OS X has a similar, but different, problem to Windows XP. On Mac, If you look at Activity Monitor it will look like we’re using more memory than we actually are. The short summary is Windows Vista (Commit Size) and Linux (RSS) provide pretty accurate memory measurement numbers while Windows XP and MacOS X do not. One portion of Stuart’s blog post that I found to be particularly interesting was the discussion of measuring cross-platform browser memory use – and how difficult it can be. I, personally, use OS X and am interested to see the memory numbers there as well. Now, obviously, Windows Vista isn’t the only platform available. It far excels anything that we offered, previously, and seems to best all other browsers on the platform. It’s great to see the massively-improved memory use of Firefox 3. Some preliminary numbers show Safari 3 on a similar path to IE 7 (Stuart mentioned that IE 8 showed a similar path, as well). Note that both Safari 3 and IE 8 crashed during the test (which was a page runner which automatically opened and closed groups of web pages) so accurate numbers weren’t able to be achieved for them. For example, here’s the results from Windows Vista of a number of browsers:
I borrowed some of his data and created another view of the results. I highly recommend that you check it out. (I also observed iceweasel loosing memory on the rpi.) This works on my 2G netbook and 4G laptop.Mozilla developer ‘Pavlov’ wrote up some extensive details on memory use in Firefox 3. To make sure I don't crash my Windows PCs, I set the nf file webcam_limit to 180 frames, or about 3 minutes at 1 frame/sec. The only way to recover memory is to close FF. Memory leaks with FF have been a problem for a long time, but even current FF v.23.0.1 leaks memory when viewing mjpegs. Eventually there's no "free" or "available" memory. Investigation with Task Manager and Resource Monitor on PC showed a chunk of memory was used up for every frame displayed in FF and wasn't returned to Windows OS. While viewing the stream with Firefox 23, my 2 windows 7 PCs would sometimes crash after viewing for a while. I currently stream 800x448 (modulo 16 safe) images of my outdoor aviary to home network and on the internet. It works decently well with the motion program. I setup a MS LifeCam HD3000 on a rev B rpi.
0 kommentar(er)
