OS/2, eCS & ArcaOS - Technical > Internet

FirefFox feedback

(1/3) > >>

karotlopj:
In my opinion FireFox is the single most important program which runs on OS/2 and am really happy to be able to use it.

It's annoying that it crashes so often (three or four times a day), although I realise that it is in development and that there isn't an army of programmers developing it on OS/2, and I know Dave provides excellent support on this forum, and probably countless other lists/groups/fora.

I just wondered which was the best place to provide feedback...

Greggory Shaw:

--- Quote from: John Poltorak on May 27, 2016, 01:20:45 pm ---I just wondered which was the best place to provide feedback...

--- End quote ---

Did you read the README.OS2 file ?

Dave Yeo:
Why are you getting so many crashes? I run SeaMonkey, mostly the same code and it is very stable here as long as I restart the computer every few days due to shared memory slowly leaking away. Had one sys3171 in pixman.
Have you installed exceptq along with the dbg files? If so are you getting trp files in your program directory?
Did you mark the DLLs to load high?
There is an issue tracker at Github if you want to file a bug report

Doug Bissett:

--- Quote ---Why are you getting so many crashes?
--- End quote ---

Now that is a good question. Of course, if anybody knew the answer, the problem could probably be fixed.

I have exceptq installed (latest that I know about), and I don't get any TRP files, but FF (38.2.1) causes a PROCDUMP about 50% of the time when I shut it down. I can see no reason why that would happen. The FF DLLs get loaded low, and I use Free Shared Mem to monitor for a shortage of shared memory. It is almost always more than 128 megs free.

I have had problems with AOO 4.1.2, which has the DLLs set to load high. Since it crashes at every shutdown (yes, I DO have the updated kernel), I use the quick start feature, to keep it loaded, which works. If I try to load the AOO DLLs low, and start FF while AOO is running, it is an instant hang condition, every time.

Now, the really odd problem is that sometimes I can reboot, and the system will run for several days, with no problems. At other times, it will crash, or hang, after a few hours, but only when I am using FF. Free Shared Mem usually indicates a sudden drop in available shared memory, when that happens, but it still shows about 75 meg of free shared memory (which could be gone before it can show it). Using VIRTUALADDRESSLIMIT=3072 has improved the situation, but it has not fixed the problem. I am suspicious that there is some sort of startup conflict that is causing trouble, but I have not been able to isolate it. I will note, that when it runs for longer periods of time, that Free Shared Mem is showing about 160 meg of free shared memory, and it doesn't seem to drop.

Dariusz Piatkowski:
My comments are regarding FF 17.x, but for what it's worth:

1) I re-boot my machine as little as possible...usually every 10 days or so, mostly because the low shared memory problem starts to impact WPS

2) usually i have anywhere between 7-10 FF windows open, most with about 5 tabs each, these stay up and running at all times, "about:memory" usually shows about 1Gig used

3) when FF dies it does so with a gracefull exit...so no hangs, etc, etc...occasionally I may encounter a problem and can NOT kill FF...that usually requires a re-boot

Navigation

[0] Message Index

[#] Next page

Go to full version