Re: frequent SeaMonkey crashes
On 05/06/18 22:53, Riccardo Mottola wrote: > Hi, > > after 6.3 upgade (with associated packages) I experience very frequent > crashes of the SeaMonkey browser. > I checked RAM consumption and it crashes even if it is not very hight, > around 400MB, for example. > > I tried starting it from a terminal and see this message after a crash: > > seamonkey: Fatal IO error 12 (Cannot allocate memory) on X server :0. > > Is it a bug perhaps_ or some limit i can extend? Add your user to the "staff" login class and increase "datasize-cur" to 3072M (which corresponds to the value in the SIZE column in top for the SeaMonkey process, not with the smaller RES). Unfortunately, latest SeaMonkey consumes considerably more RAM… And it's not their fault, this is something that comes with the rendering engine in Firefox 52 ESR. So now you'll need a machine with 2GB of RAM to run it smoothly on amd64 ( I think, have kept my oldest hardware on 6.2 because of this, among others). But with the increased limit you'll get a VERY stable SeaMonkey, have used it intensively since the RC days with no crashes on two machines. It's the browser I use daily for work-related stuff. > > I tried FireFox and it seems a little bit better: strange though, > because usually it is has always been the other way and I am a long-time > seamonkey fan. I don't know what version of Firefox you use. I have 59 here and it definitely uses more RAM compared to SeaMonkey when opening lots of tabs (20-30). Of course, it's not the same Mozilla profile, and the sessions are also different, but I use more or less the same settings and extensions. However, Firefox has multiple processes per launched instance, so it probably hits the "datasize-cur" limit later for your use case. Also, these Firefox Quantum releases are really nice, anyone still using Firefox ESR 52 should check them out, as they are considerably snappier. Beware of incompatible extensions, so save your profile before trying Firefox Quantum, just in case. Maybe worth starting from scratch or with the settings saved through the Firefox account in Mozilla's cloud… Also, relevant for people running -stable: https://undeadly.org/cgi?action=article=20170425173917. signature.asc Description: OpenPGP digital signature
Re: frequent SeaMonkey crashes
Hello Riccardo, On 05/06/18 21:53, Riccardo Mottola wrote: > Hi, > > after 6.3 upgade (with associated packages) I experience very frequent > crashes of the SeaMonkey browser. > I checked RAM consumption and it crashes even if it is not very hight, around > 400MB, for example. > > I tried starting it from a terminal and see this message after a crash: > > seamonkey: Fatal IO error 12 (Cannot allocate memory) on X server :0. You can try to extend your data area size via ulimit -d. See ksh(1) for more information. Don't forget to start SeaMonkey via that same shell as well, changing the data area only works for child- programs, not the entire X login session. If this works for you you can increase the limit permanent via /etc/login.conf (which will increase the limit for all applications) or by creating a wrapper-script which will increase the limit before executing SeaMonkey. Hope this helps. > > Is it a bug perhaps_ or some limit i can extend? > > I tried FireFox and it seems a little bit better: strange though, because > usually it is has always been the other way and I am a long-time seamonkey > fan. > > Riccardo > martijn@
Re: frequent SeaMonkey crashes
On Sun, 6 May 2018, Riccardo Mottola wrote: after 6.3 upgade (with associated packages) I experience very frequent crashes of the SeaMonkey browser. I think, the problem is the upgrade of seamonkey, not of OpenBSD. I had and have the same problem with firefox, I did a lot of things that I do not remember exactly, and it got better. Perhaps the best to do is, to save what you want to save (bookmars), deleete the .mozila directory and beginn from 0. BTW, I also deactivated the only plugin automatically installed by firefox. Rodrigo.
frequent SeaMonkey crashes
Hi, after 6.3 upgade (with associated packages) I experience very frequent crashes of the SeaMonkey browser. I checked RAM consumption and it crashes even if it is not very hight, around 400MB, for example. I tried starting it from a terminal and see this message after a crash: seamonkey: Fatal IO error 12 (Cannot allocate memory) on X server :0. Is it a bug perhaps_ or some limit i can extend? I tried FireFox and it seems a little bit better: strange though, because usually it is has always been the other way and I am a long-time seamonkey fan. Riccardo
