OS/2, eCS & ArcaOS - General > Events
Firefox problem, was Re: IRC speakup with BWW this Saturday (3 of March)!
Neil Waldhauer:
The transcript of BWW speakup is now up on the VoiCE website. I can see that the topic never came up.
I'm not looking for a "resolution" to problems with Firefox -- I have all the latest libraries on both eCS and ArcaOS. I know there is a lot of work going on by looking at checkins on github, but I don't know the goal of those checkins.
I will say that marking code to load high does make some difference to stability, and I'll comment again on this in a few weeks when I have more information. I think the highmem tool could be a little more user-friendly.
I don't think I can enter a bug report for "what are you guys trying to do with Firefox?"
Silvan said in the speakup that a browser is essential to the life of the operating system. How essential is a web browser to the success of the operating system? I can browse on a smartphone or tablet. There is no platform with a bug-free browser. Still, I'm inclined to think he's right. I'm using Firefox on ArcaOS to type this message.
David Graser:
Firefox does what I call CPU trashing. Based on the CPU monitor, it is extremely high. Seamonkey does te same thing, but is nowhere near as high as Firefox. Right now I will use Seamonkey since it does a better job utilizing the CPU.
Dave Yeo:
Hi, currently Bitwise is trying to get all of the Mozilla testsuite to run and pass, not a small job as it hasn't even worked since about FFv4 when Walter did a lot of work on it. The testsuite is what Mozilla expects to pass before releases and even after new commits.
So far, he has fixed a couple of memory related problems including fixes to libc and/or libcx and moved from mmap to native memory allocation in places. There's no way to say if running the testsuite will show our problems but it is a good start.
Currently dmik is trying to implement some type of tracing to see where the code is spending its time. Hopefully that'll help but Mozilla uses lots of JS, XUL and such to draw the browser so who knows.
As for SM being currently faster then FF, it is probably a newer build depending on which FF is used. I was also experimenting with different compiler options, eg optimizing for size rather then speed, which may be why the DLLs were different sizes. Unluckily enough time has gone by that I forget exactly what I did. about:buildconfig will show the compiler flags I (and dmik) used with -Os being for size and -O3 for speed. Probably best is -O3 for the JavaScript engine and -Os for the rest, smaller binaries take less memory.
Here I find that SM performance is great if started in safe-mode and as extensions are enabled, it gets worst, especially some extensions. TB is worse and just mouse overing it can peak both cores for seconds.
A lot of these problems are possibly intrinsic to the design of Mozilla and that is one reason that they're moving to the Quantum rendering engine. Other things are getting worse with all browsers as they split it into multiple processes for various reasons, mostly security.
David Graser:
I had to move back to Firefox. Seamonkey would run for awhile and then would suddenly terminate.
What is wierd is that on my lastest bootup, Firefox CPU trashing is way down, I can't explain it. Before I could barely use Firefox. Right now it is pleasant to use.
Doug Bissett:
There are two things, that I find will help Firefox (and probably the other Mozilla variants). One is to use a small cache. I set it to 50 MB. Of course, individual setups may work better with other sizes.
The other is to use ANPM (RPM/YUM) to install FFMPEG. be careful there because FFMPEG will want to install the sdl (lower case) package, while other things need the SDL (upper case) package. Install SDL (upper case) first. If you already have sdl (lower case) installed, uninstall it (and watch what other packages get uninstalled with it). Then install SDL, and the other packages that got uninstalled, then install FFMPEG.
Those are not going to make FF work perfectly, but I find that it helps.
--- Quote ---I can't explain it. Before I could barely use Firefox. Right now it is pleasant to use.
--- End quote ---
It is possible, that you got a bad web page into the cache, and going back to that web page would try to load the bad page. Eventually, that bad page would work it's way out of the cache, fixing the problem. I try to remember to clear the cache, after a crash.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version