OS/2, eCS & ArcaOS - Technical > Internet
Mozilla Warpin installers + applications
Boris:
Dave, so you can't improve bitwise's FF17 the same way you did with FF10? I mean more aggressive use of highmem?
That's very important -- reducing the use of low memory, really.
Dave Yeo:
At this point the Bitwise build seems to work pretty good and much the same as my build and I don't think it would be a good idea to have 2 different versions of Firefox floating around. They're the ones who'll be fixing most bugs and I don't want to introduce any subtle problems that are caused by things like different build environments.
Boris:
Dave, the build works pretty bad. Although it even doesn't crash too often (while a lot people say it does), the biggest problem is that it fucks up the shared memory arena and I can't run programs even after I close FF (sic!), also it doesn't free memory at all -- closing tabs doesn't increase the amount of free memory in the system. Also when I open tabs back again, it eats even more memory, so that's literally a memory-waste-machine.
Dave Yeo:
You could open an issue at github and ask for them to do a new build with -Zhigh-mem added to the enable-optimize flags.
Doug Bissett:
--- Quote from: Boris on March 29, 2014, 07:51:38 pm ---Dave, the build works pretty bad. Although it even doesn't crash too often (while a lot people say it does), the biggest problem is that it <censored> up the shared memory arena and I can't run programs even after I close FF (sic!), also it doesn't free memory at all -- closing tabs doesn't increase the amount of free memory in the system. Also when I open tabs back again, it eats even more memory, so that's literally a memory-waste-machine.
--- End quote ---
Strange. I just did a quick test with FF 17.0.5 beta2 (which works well, for me). I don't see low memory usage change, at all, after starting the program. Shared high memory doesn't change, just by opening tabs. It does go down a bit when those tabs are populated. I didn't see the memory returned until I closed FF. There is, of course, some memory that doesn't get returned, but that seems to be normal for most programs.
FWIW, the worst shared memory eater, that I have seen, is CLAMD.EXE, and it gets worse with every database update. I had to quit using that more than a year ago. Since then, I have had no trouble with shared memory.
One thing, that seems to help with shared memory space, is to have the line
dllbasing=off
near the top of your CONFIG.SYS. That allows OS/2 to make better use of shared memory, at the expense of a very slight decline in performance (not noticeable, unless you are still using a 486 SX processor).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version