firefox for mobiles

[David Ford]

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.
>