firefox for mobiles

[Bradley Hook]

While FF does have a fairly large footprint, I've never had these kinds
of memory consumption problems. I generally leave my FF sessions open
for days or weeks at home, and I simultaneously load 3D games, OOo,
graphics apps, and other stuff without ever having trouble with memory
(granted I do have 2GB).

However, even the large memory footprint that I do see has an
explanation, and can be tuned by tweaking about:config. By default, FF
caches every page loaded on every tab for that sessions. If you consider
a geek's multi-day surfing session, that is a lot of data to cache, and
the cache data also can't be compressed. Since the primary target of FF
is the "average" user -- which has several short surfing sessions and
usually closes the browser between sessions -- the default settings make
sense. If this is not your surfing style, then change your settings.

That said, the full blown browser would be an awfully hefty app to put
on a phone, and the minimo browser is currently targeting windows
portables. Why not go with something with a tiny footprint, time-tested
and proven.... lynx anyone?

~Bradley

David Ford wrote:
> It behaves far better on my laptop as well, I strongly suspect it has
> something to do with the 64bit nature of my desktop vs 32 for all other
> places I use it.  My 64bit firefox is currently taking 1.8G of ram after
> having been started ~16 hours ago.
> 
> Several groups of people, myself included, have submitted valgrind
> outputs that show massive memory hemorrhaging but the reports pretty
> much get ignored. :(
> 
> More debug tools would go a long way towards letting the community find
> and fix these issues and make FF something desirable on the neo.
> 
> I love the idea of the neo, but it's just too small in cpu/ram for some
> other (really neat) ideas. I'm impatient :D
> 
> -david
> 
> Ian Stirling wrote:
>> David Ford wrote:
>>> If it's anything like mozilla/firefox now, we're gonna need a hefty
>>> battery, hugely more cpu, and about 1G of ram onboard.
>> Oddly.
>> It seems to behave OK on my laptop - 1.5 - which I was using for some
>> time with 128M RAM.
>> Admittedly, it did need restarted every day or three.
>>
>> The big problem is the lack of debug tools.
>>
>> I write a new extension.
>> I then want to profile it, to find out how much CPU, and how much CPU
>> it makes the core use.
>> I can't.
>> Worse, the same problem applies to most of the XUL/XBL/JS core.
>>
> 
> _______________________________________________
> OpenMoko community mailing list
> community at lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
> 
>