Mozilla Stabilizes Firefox 18

CommanderFrank

Cat Can't Scratch It
Joined
May 9, 2000
Messages
75,399
Less than two weeks ago Mozilla rolled out Firefox 18 only to discover the release had three stability issues. Mozilla has released a fix in Firefox 18.0.1 to rectify the problems. So much for beta testing. :D

The update should be automatically downloaded by Firefox on Windows and Mac OS X. Linux users whose Firefox has been provided by their distribution should expect system updates which include the update.
 
Is this meant to make me feel better about the concept of "keeping up-to-date"? It sounds to me like the cure is worse than the disease.
 
18 was a pig and slow as hell. Not sure what happened or how it even got out the door, but 18.0.1 seems to have solved some issues.
 
People should just move to Waterfox now if they have a 64 bit OS.

Yes, because if your problem is that your web browser is using 4GB of memory...the logical solution is to provide it more addressable memory.
 
People should just move to Waterfox now if they have a 64 bit OS.
Or just run Linux where 64-bit firefox builds have been standard for years.
KvLAjBq.png
 
I actually just switched back to FF after using Chrome the past year or so. Chrome was giving me all sorts of fits, slow downloads, random images not loading or videos, and just overall everything was slower.

FF 18.0.1 is running much better than Chrome did for me.
 
It had a stability issue? I never noticed. (no sarcasm)
 
Or just run Linux where 64-bit firefox builds have been standard for years.
KvLAjBq.png

what the hell are you doing that you need 6.9GB of virtual memory and 96% CPU resource in Firefox, not counting plug-ins?
 
what the hell are you doing that you need 6.9GB of virtual memory and 96% CPU resource in Firefox, not counting plug-ins?

Virt refers to the amount of virtual address space a program is using. Firefox can easily get that high if left running for a long time, especially 64-bit versions (address space cleanup is only triggered when one is running low on it) because of fragmentation; memory must be allocated into contiguous blocks; deallocating memory leaves a bunch of small unused blocks in the address space that can't be used as they don't provide enough contiguous space.

35. VIRT -- Virtual Memory Size (KiB)
The total amount of virtual memory used by the task. It includes all code, data and shared libraries plus pages
that have been swapped out and pages that have been mapped but not used.

UNIX systems traditionally measure CPU usage by percentage of a single processor. 100% = 1 Core, 200% = 2 Cores and so on.
 
Virt refers to the amount of virtual address space a program is using. Firefox can easily get that high if left running for a long time, especially 64-bit versions (address space cleanup is only triggered when one is running low on it) because of fragmentation; memory must be allocated into contiguous blocks; deallocating memory leaves a bunch of small unused blocks in the address space that can't be used as they don't provide enough contiguous space.



UNIX systems traditionally measure CPU usage by percentage of a single processor. 100% = 1 Core, 200% = 2 Cores and so on.

So basically what I already said only with a less direct reference to memory leaks and porn.
 
what the hell are you doing that you need 6.9GB of virtual memory and 96% CPU resource in Firefox, not counting plug-ins?
I have a problem with not closing tabs. :p I think when I finally killed it after taking that screenshot, I had ~250 tabs open and Firefox had been running for over 2 weeks.
 
Back
Top