On Mon, 28 Jan 2013 21:32:59 +0100 Eric Huiban <gro...@grompf.net> wrote:
> On 01/28/13 13:43, Ed Ahlsen-Girard wrote: > > On Fri, 25 Jan 2013 01:55:35 +0100 > > Eric Huiban <gro...@grompf.net> wrote: > > > >> On 01/23/13 01:43, Salil Wadnerkar wrote: > >>> Hi, > >>> > >>> On my amd64 machine, firefox crashes regularly after some time. > >>> > >>> [...] > >>> > >>> $ uname -a > >>> OpenBSD passport.my.domain 5.2 GENERIC.MP#17 amd64 > >>> > >>> I am on OpenBSD current and I have my system and packages updated > >>> just yesterday. > >>> > >>> Thanks > >>> Salil > >>> > >>> > >> > >> Your firefox does not crash by itself. It is wiped out by the > >> system when the process size reaches the maximum memory size you > >> allowed to be requested by your user. > >> > >> Already seen with 5.1, 5.2 and if what i'm remembering is correct > >> 5.0. (No change made on any binaries). Memory size can increase a > >> lot when using a lot of tabs at the same time, or after loading > >> pages overloaded with crappy scripts for advertisement display. > >> All this modulates the delay before firefox relaunch... > >> > >> Sorry for my poor english wording. Not my native language. > >> > > > > Perhaps this is related, perhaps not, but my firefox issue is that > > the system becomes unresponsive as more tabs/certain pages (ads, > > videos) are opened. Completely unresponsive: can't ssh in over the > > network (I'd try serial but I can't find my cable). dmesg below. > > Time to try Chrome? > > > > I observed the same behaviour. I have to wait a little bit for the > "application killing" by the system, or just have to press quietly > two times the "close" button on the window upper "bar" : then the > window manager proposes me to close the unresponsive application. > I waited overnight, and it made no difference. The system does not respond to either the mouse or the keyboard. -- Edward Ahlsen-Girard Ft Walton Beach, FL
