Re: Firefox: Recenty instable
> Which mirror is your favourite? I was using [1] which I found was almost 2 weeks behind and then switched to [2]. [1] http://ftp2.eu.openbsd.org/ [2] https://ftp.hostserver.de/
Re: Firefox: Recenty instable
On 2017-03-13, Mihai Popescuwrote: > I still have some suprise to see that my favorite mirror is many days > behind snapshots from the time point of view. Maintenance, perhaps? Which mirror is your favourite?
Re: Firefox: Recenty instable
Hi, On Thu, 16 Mar 2017 12:29:00 +0100 Sebastien Mariewrote: > > What did you raise it to? I raised mine to 1536M for both -cur and -max > > and it's had no visible effect. > > Sorry, but 1.5 Go could be a small value currently... Javascript JIT > engine pre-allocate 1 Go for itself at startup, and next the application > needs to do some malloc too... > > You could check the effective current value (datasize-cur) with: > > ksh$ ulimit -d# value in kbytes > 786432 > > Or read the value configured in login.conf: > > $ getcap -f /etc/login.conf -s datasize-cur default staff > default: 768M > staff: 1536M > > For obtain your current login-class: > > $ id -c > default I am currently running with the following and have no problems so far: $ getcap -f /etc/login.conf -s datasize-cur default staff default: 768M staff: 2560MM $ ulimit -d 2621440 $ id -c staff regards Lars
Re: Firefox: Recenty instable
On Wed, Mar 15, 2017 at 10:00:33PM -0500, Ed Ahlsen-Girard wrote: > On Sun, 12 Mar 2017 23:47:36 +0100 > Thomas Weinbrennerwrote: > > > Since raising datasize-cur in /etc/login.conf my firefox has stopped > > crashing. > > > > What did you raise it to? I raised mine to 1536M for both -cur and -max > and it's had no visible effect. Sorry, but 1.5 Go could be a small value currently... Javascript JIT engine pre-allocate 1 Go for itself at startup, and next the application needs to do some malloc too... You could check the effective current value (datasize-cur) with: ksh$ ulimit -d # value in kbytes 786432 Or read the value configured in login.conf: $ getcap -f /etc/login.conf -s datasize-cur default staff default: 768M staff: 1536M For obtain your current login-class: $ id -c default Thanks. -- Sebastien Marie
Re: Firefox: Recenty instable
On Sun, 12 Mar 2017 23:47:36 +0100 Thomas Weinbrennerwrote: > On Sun, Mar 12, 2017 at 11:19:18PM +0100, Stefan Wollny wrote: > [...] > > [...] > > [...] > > I found this quite helpful. > > https://marc.info/?l=openbsd-ports=148925156914633 > > Since raising datasize-cur in /etc/login.conf my firefox has stopped > crashing. > What did you raise it to? I raised mine to 1536M for both -cur and -max and it's had no visible effect. -- Edward Ahlsen-Girard Ft Walton Beach, FL
Re: Firefox: Recenty instable
> for the last 3~4 days (always running the latest of public amd64-current) I'm not sure what you mean by -current. From what you posted: > OpenBSD 6.1-beta (GENERIC.MP) #7: Sat Mar 11 18:32:03 MST 2017 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP You forgot to tell the firefox version package. Here is what I have: OpenBSD 6.1-beta (GENERIC.MP) #214: Mon Mar 6 15:56:51 MST 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP firefox-51.0p0 I have no single issue with firefox in my browsing. I still have some suprise to see that my favorite mirror is many days behind snapshots from the time point of view. Maintenance, perhaps?
Re: Firefox: Recenty instable
On Sun, Mar 12, 2017 at 11:19:18PM +0100, Stefan Wollny wrote: > Hi there, > > for the last 3~4 days (always running the latest of public > amd64-current) firefox behaviour was kind of "unfamiliar" - regular > crashes after a few minutes. [...] > Am I right supposing that the most likely answer will be "Wait for the > next snap!"? :-) I found this quite helpful. https://marc.info/?l=openbsd-ports=148925156914633 Since raising datasize-cur in /etc/login.conf my firefox has stopped crashing.