Quantcast

firefox 52 and whatsapp web client

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
19 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

firefox 52 and whatsapp web client

frantisek holop
it seems that i can 100% crash firefox by trying to use
the web.whatsapp.com client for varying lengths of
time.  this seems to be a regression, is anyone else
seeing this?

-f
--

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: firefox 52 - crashes at startup or later due to oom

Sebastien Marie-3
On Sun, Mar 12, 2017 at 10:00:55PM +0100, frantisek holop wrote:
> it seems that i can 100% crash firefox by trying to use
> the web.whatsapp.com client for varying lengths of
> time.  this seems to be a regression, is anyone else
> seeing this?
>

with firefox-52.0, the way memory allocation is done for javascript has
changed:

  - Bug 1334933 - Allocate executable pages from a pre-reserved range.
    https://hg.mozilla.org/releases/mozilla-release/rev/6b35bbf96b67

and in the same release, the size of initial malloc has been raised from
640Mo to 1Go:

  - Bug 1337561 - Baldr: call largeAllocationCallback and retry if executable allocation fails. r=jandem, a=jcristau
    https://hg.mozilla.org/releases/mozilla-release/rev/65bb26d07408


It makes firefox to malloc a chunk of 1Go at startup.

As you crash after the start, I assume you are running in "staff" class
or have modified login.conf datastack-cur value in "default" class.

The current way to deal with that is to raise your datastack-cur to make
firefox to fit in...


Alternatively, I would be glad if someone could test the diff below: I
run with it, but I don't use javascript enough to be sure the allocation
isn't too low.

It makes the allocation to be 128 Mo instead of 1 Go on 64bits platform
(it is the same value than for 32 bits platform in fact).

Note that the value is the total allocated bytes for javascript. It
isn't a initial value, and it shouldn't grow (if I correctly understand
the code). So I expect 128 Mo to be a bit "restrictive".

Thanks.
--
Sebastien Marie


Index: Makefile
===================================================================
RCS file: /cvs/ports/www/mozilla-firefox/Makefile,v
retrieving revision 1.311
diff -u -p -r1.311 Makefile
--- Makefile 7 Mar 2017 15:31:38 -0000 1.311
+++ Makefile 13 Mar 2017 05:27:26 -0000
@@ -5,6 +5,7 @@ COMMENT = Mozilla web browser
 # Don't forget to bump www/firefox-i18n after updates.
 
 MOZILLA_VERSION = 52.0
+REVISION = 0
 MOZILLA_BRANCH = release
 MOZILLA_PROJECT = firefox
 MOZILLA_CODENAME = browser
Index: patches/patch-js_src_jit_ProcessExecutableMemory_cpp
===================================================================
RCS file: patches/patch-js_src_jit_ProcessExecutableMemory_cpp
diff -N patches/patch-js_src_jit_ProcessExecutableMemory_cpp
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ patches/patch-js_src_jit_ProcessExecutableMemory_cpp 13 Mar 2017 05:27:26 -0000
@@ -0,0 +1,13 @@
+$OpenBSD$
+Allocate only few bytes for javascript
+--- js/src/jit/ProcessExecutableMemory.cpp.orig Sat Mar 11 13:28:15 2017
++++ js/src/jit/ProcessExecutableMemory.cpp Sun Mar 12 06:01:39 2017
+@@ -390,7 +390,7 @@ class PageBitSet
+ #if JS_BITS_PER_WORD == 32
+ static const size_t MaxCodeBytesPerProcess = 128 * 1024 * 1024;
+ #else
+-static const size_t MaxCodeBytesPerProcess = 1 * 1024 * 1024 * 1024;
++static const size_t MaxCodeBytesPerProcess = 128 * 1024 * 1024;
+ #endif
+
+ // Per-process executable memory allocator. It reserves a block of memory of

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: firefox 52 - crashes at startup or later due to oom

Tinker
On 2017-03-13 05:34, Sebastien Marie wrote:
..
> Note that the value is the total allocated bytes for javascript. It
> isn't a initial value, and it shouldn't grow (if I correctly understand
> the code). So I expect 128 Mo to be a bit "restrictive".
..
> +-static const size_t MaxCodeBytesPerProcess = 1 * 1024 * 1024 * 1024;
> ++static const size_t MaxCodeBytesPerProcess = 128 * 1024 * 1024;

So Firefox has a blanked fixed-heap size model for all of its
deployments??

If so, that is like, ridiculously archaic, what were they thinking. I
wonder if it can be made to run in a dynamic heap model. I can't see why
Wikipedia and alert("Hello world"); would take up any much memory at
all, like, more than the binary and dep libraries + 1-100MB allocations.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: firefox 52 - crashes at startup or later due to oom

Theo de Raadt-2
> On 2017-03-13 05:34, Sebastien Marie wrote:
> ..
> > Note that the value is the total allocated bytes for javascript. It
> > isn't a initial value, and it shouldn't grow (if I correctly understand
> > the code). So I expect 128 Mo to be a bit "restrictive".
> ..
> > +-static const size_t MaxCodeBytesPerProcess = 1 * 1024 * 1024 * 1024;
> > ++static const size_t MaxCodeBytesPerProcess = 128 * 1024 * 1024;
>
> So Firefox has a blanked fixed-heap size model for all of its
> deployments??
>
> If so, that is like, ridiculously archaic, what were they thinking. I
> wonder if it can be made to run in a dynamic heap model. I can't see why
> Wikipedia and alert("Hello world"); would take up any much memory at
> all, like, more than the binary and dep libraries + 1-100MB allocations.

Yet again the diff in your email didn't come through!

Are you using some weird encoding that the project mailserver doesn't
allow through?

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: firefox 52 - crashes at startup or later due to oom

Tinker
In reply to this post by Tinker
On 2017-03-13 05:40, Tinker wrote:

> On 2017-03-13 05:34, Sebastien Marie wrote:
> ..
>> Note that the value is the total allocated bytes for javascript. It
>> isn't a initial value, and it shouldn't grow (if I correctly
>> understand
>> the code). So I expect 128 Mo to be a bit "restrictive".
> ..
>> +-static const size_t MaxCodeBytesPerProcess = 1 * 1024 * 1024 * 1024;
>> ++static const size_t MaxCodeBytesPerProcess = 128 * 1024 * 1024;
>
> So Firefox has a blanked fixed-heap size model for all of its
> deployments??

(typo: "blanked" should be "blanket".)

>
> If so, that is like, ridiculously archaic, what were they thinking. I
> wonder if it can be made to run in a dynamic heap model. I can't see
> why Wikipedia and alert("Hello world"); would take up any much memory
> at all, like, more than the binary and dep libraries + 1-100MB
> allocations.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: firefox 52 - crashes at startup or later due to oom

Tinker
In reply to this post by Theo de Raadt-2
On 2017-03-13 05:43, Theo de Raadt wrote:
..
> Yet again the diff in your email didn't come through!
>
> Are you using some weird encoding that the project mailserver doesn't
> allow through?

My fiften-million-two-hundred-thousand-lines initial light warmup diff
for Firefox codebase uncrapping cleanup somehow got stuck on the way.
Dough.

(On a more real note thanks for insisting that I contribute. I do though
not code right now.)

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: firefox 52 - crashes at startup or later due to oom

Landry Breuil-5
In reply to this post by Tinker
On Mon, Mar 13, 2017 at 05:40:25AM +0000, Tinker wrote:

> On 2017-03-13 05:34, Sebastien Marie wrote:
> ..
> > Note that the value is the total allocated bytes for javascript. It
> > isn't a initial value, and it shouldn't grow (if I correctly understand
> > the code). So I expect 128 Mo to be a bit "restrictive".
> ..
> > +-static const size_t MaxCodeBytesPerProcess = 1 * 1024 * 1024 * 1024;
> > ++static const size_t MaxCodeBytesPerProcess = 128 * 1024 * 1024;
>
> So Firefox has a blanked fixed-heap size model for all of its deployments??
>
> If so, that is like, ridiculously archaic, what were they thinking. I wonder
> if it can be made to run in a dynamic heap model. I can't see why Wikipedia
> and alert("Hello world"); would take up any much memory at all, like, more
> than the binary and dep libraries + 1-100MB allocations.

Talking about it here won't help. Take that upstream.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: firefox 52 - crashes at startup or later due to oom

Landry Breuil-5
In reply to this post by Sebastien Marie-3
On Mon, Mar 13, 2017 at 06:34:12AM +0100, Sebastien Marie wrote:

> On Sun, Mar 12, 2017 at 10:00:55PM +0100, frantisek holop wrote:
> > it seems that i can 100% crash firefox by trying to use
> > the web.whatsapp.com client for varying lengths of
> > time.  this seems to be a regression, is anyone else
> > seeing this?
> >
>
> with firefox-52.0, the way memory allocation is done for javascript has
> changed:
>
>   - Bug 1334933 - Allocate executable pages from a pre-reserved range.
>     https://hg.mozilla.org/releases/mozilla-release/rev/6b35bbf96b67
>
> and in the same release, the size of initial malloc has been raised from
> 640Mo to 1Go:
>
>   - Bug 1337561 - Baldr: call largeAllocationCallback and retry if executable allocation fails. r=jandem, a=jcristau
>     https://hg.mozilla.org/releases/mozilla-release/rev/65bb26d07408
>
>
> It makes firefox to malloc a chunk of 1Go at startup.
>
> As you crash after the start, I assume you are running in "staff" class
> or have modified login.conf datastack-cur value in "default" class.
>
> The current way to deal with that is to raise your datastack-cur to make
> firefox to fit in...
>
>
> Alternatively, I would be glad if someone could test the diff below: I
> run with it, but I don't use javascript enough to be sure the allocation
> isn't too low.
>
> It makes the allocation to be 128 Mo instead of 1 Go on 64bits platform
> (it is the same value than for 32 bits platform in fact).

Yet, firefox is unusable on 32-bit hardware. Try *running* it on an atom
netbook with 1Gb RAM... so taking the same value as 32 bits platforms
isnt an argument :)

From what i read in the various related bugs, the size was increased to
fix memory allocation crashes when running WASM (the new 'assembly in
javascript' standard) and i think to increase randomization of memory
addresses allocated. *shrug*

For us, i think coming back to 640M is the "safest" solution.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: firefox 52 - crashes at startup or later due to oom

Peter N. M. Hansteen-3

On 03/13/17 08:01, Landry Breuil wrote:

>> Alternatively, I would be glad if someone could test the diff below: I
>> run with it, but I don't use javascript enough to be sure the allocation
>> isn't too low.
>>
>> It makes the allocation to be 128 Mo instead of 1 Go on 64bits platform
>> (it is the same value than for 32 bits platform in fact).
>
> Yet, firefox is unusable on 32-bit hardware. Try *running* it on an atom
> netbook with 1Gb RAM... so taking the same value as 32 bits platforms
> isnt an argument :)
>
>>From what i read in the various related bugs, the size was increased to
> fix memory allocation crashes when running WASM (the new 'assembly in
> javascript' standard) and i think to increase randomization of memory
> addresses allocated. *shrug*
>
> For us, i think coming back to 640M is the "safest" solution.

I've been seeing the same symptoms (firefox-52 crashes with various out
of memory errors after a few minutes).

What is the most useful way to help debug this? Tweaking staff's
stacksize-cur upwards, or some other value?

I did some limited experiments tonight, but I'm afraid I started too
late to get as far as seeing any useful conclusions.

But I can try again tomorrow afternoon CET (possibly with new snapshot
and packages).

All the best,
Peter

--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: firefox 52 - crashes at startup or later due to oom

Sebastien Marie-3
On Mon, Mar 13, 2017 at 11:19:09PM +0100, Peter N. M. Hansteen wrote:

>
> On 03/13/17 08:01, Landry Breuil wrote:
> >> Alternatively, I would be glad if someone could test the diff below: I
> >> run with it, but I don't use javascript enough to be sure the allocation
> >> isn't too low.
> >>
> >> It makes the allocation to be 128 Mo instead of 1 Go on 64bits platform
> >> (it is the same value than for 32 bits platform in fact).
> >
> > Yet, firefox is unusable on 32-bit hardware. Try *running* it on an atom
> > netbook with 1Gb RAM... so taking the same value as 32 bits platforms
> > isnt an argument :)
> >
> >>From what i read in the various related bugs, the size was increased to
> > fix memory allocation crashes when running WASM (the new 'assembly in
> > javascript' standard) and i think to increase randomization of memory
> > addresses allocated. *shrug*
> >
> > For us, i think coming back to 640M is the "safest" solution.
>
> I've been seeing the same symptoms (firefox-52 crashes with various out
> of memory errors after a few minutes).
>
> What is the most useful way to help debug this? Tweaking staff's
> stacksize-cur upwards, or some other value?
>

the root cause of the segfault is known: firefox allocate a big chunk of
1Go for javascript, and still allocate some memory for others parts of
firefox. so the program will hit RLIMIT_DATA very quickly.

so you had to adjust the datastack-cur limit in your login-class (staff
or default depending the user).

I experimented several things:
  - make firefox allocate only 128 Mo for javascript. it works for me,
    but I am not a big user of javascript.

  - make firefox allocate only 640 Mo for javascript (as landry@
    proposed). it should make firefox usable in staff class, but it is
    still too much for default class (reminder: the 640 Mo is for
    javascript only, the application still do malloc() for others parts
    of firefox).

Personally, what bother me is the fact that datastack limit is the same
for all processes, without convenient way (for my knowledge) to run some
programs with alternate class (and bigger datastack).

Else, I would have a "default" login-class with something like 256 Mo of
datastack, and running firefox or libreoffice with alternate login-class
with more datastack (like 2 Go).

I only know su(1) to be able to change the login-class, and the
parameter is reserved to root (and it is normal). So if I want to use it
I have to do something like:

semarie@foo$ doas su -c bigmem semarie -c "firefox"

And I am not very confident for the use of doas(1) and su(1) in the same
command-line...


Alternatively, having a small datastack-cur and a bigger datastack-max
is a possibility, and setting datastack-cur to datastack-max before
running firefox (ulimit -d `ulimit -dH`).


If people have others suggestions, I would be glad to hear them :)

--
Sebastien Marie

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: firefox 52 - crashes at startup or later due to oom

Ted Unangst-6
Sebastien Marie wrote:
> Alternatively, having a small datastack-cur and a bigger datastack-max
> is a possibility, and setting datastack-cur to datastack-max before
> running firefox (ulimit -d `ulimit -dH`).

indeed. for some years now, i usually start firefox from a shell.

first ulimit -d 4123123, then firefox. as a bonus, you get to see all sorts of
interesting messages.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: firefox 52 - crashes at startup or later due to oom

Mikolaj Kucharski-3
On Tue, Mar 14, 2017 at 02:47:31AM -0400, Ted Unangst wrote:
> Sebastien Marie wrote:
> > Alternatively, having a small datastack-cur and a bigger datastack-max
> > is a possibility, and setting datastack-cur to datastack-max before
> > running firefox (ulimit -d `ulimit -dH`).
>
> indeed. for some years now, i usually start firefox from a shell.
>
> first ulimit -d 4123123, then firefox. as a bonus, you get to see all sorts of
> interesting messages.

Chromium has a wrapper script for datastack bumping. When I install
fresh OpenBSD that wrapper script reminds me that I forget to bump
datastack-max via xmessage(1) and makes datastack bigger when login
class is configured properly for a user. Could firefox have similar
wrapper?

--
best regards
q#

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: firefox 52 - crashes at startup or later due to oom

Landry Breuil-5
On Tue, Mar 14, 2017 at 08:22:37AM +0000, Mikolaj Kucharski wrote:

> On Tue, Mar 14, 2017 at 02:47:31AM -0400, Ted Unangst wrote:
> > Sebastien Marie wrote:
> > > Alternatively, having a small datastack-cur and a bigger datastack-max
> > > is a possibility, and setting datastack-cur to datastack-max before
> > > running firefox (ulimit -d `ulimit -dH`).
> >
> > indeed. for some years now, i usually start firefox from a shell.
> >
> > first ulimit -d 4123123, then firefox. as a bonus, you get to see all sorts of
> > interesting messages.
>
> Chromium has a wrapper script for datastack bumping. When I install
> fresh OpenBSD that wrapper script reminds me that I forget to bump
> datastack-max via xmessage(1) and makes datastack bigger when login
> class is configured properly for a user. Could firefox have similar
> wrapper?

Could, but that's just imo an ugly workaround for a broken environment.
You can't sanely run a desktop session with any browser using the
default limits anyway...

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: firefox 52 - crashes at startup or later due to oom

Sebastien Marie-3
On Tue, Mar 14, 2017 at 10:28:05AM +0100, Landry Breuil wrote:
> You can't sanely run a desktop session with any browser using the
> default limits anyway...

I disagree. I run firefox with low memory pressure:

97871 semarie    2    0  434M  320M sleep/1   poll     34:42  0.68% firefox
95072 semarie    2    0  338M  260M sleep/1   poll     27:04  0.34% firefox

(with two processes due to e10n).

My session has 12 tabs opened with 3 or 4 tabs javascript enabled. But I
agree my use of firefox isn't representative of common use-case (no
videos or other ressources consuming websites).

The running process is firefox-52.0 patched for allocating 128 Mo for
javascript (instead of 1 Go).
--
Sebastien Marie

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: firefox 52 - crashes at startup or later due to oom

David Coppa
On Tue, Mar 14, 2017 at 11:21 AM, Sebastien Marie <[hidden email]> wrote:

> On Tue, Mar 14, 2017 at 10:28:05AM +0100, Landry Breuil wrote:
>> You can't sanely run a desktop session with any browser using the
>> default limits anyway...
>
> I disagree. I run firefox with low memory pressure:
>
> 97871 semarie    2    0  434M  320M sleep/1   poll     34:42  0.68% firefox
> 95072 semarie    2    0  338M  260M sleep/1   poll     27:04  0.34% firefox
>
> (with two processes due to e10n).
>
> My session has 12 tabs opened with 3 or 4 tabs javascript enabled. But I
> agree my use of firefox isn't representative of common use-case (no
> videos or other ressources consuming websites).
>
> The running process is firefox-52.0 patched for allocating 128 Mo for
> javascript (instead of 1 Go).

Try using maps.google.com ... ;)

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: firefox 52 - crashes at startup or later due to oom

Peter N. M. Hansteen-3
In reply to this post by Sebastien Marie-3
Just a few data points from last night here - based on hastily read messages in this thread
I tried increasing the stacksize-cur value for the staff group in login.conf to see if it
made a difference. The main conclusion is that for the values I tried, it didn't really, but
detail follow.


This is with last night's packages, dmesg as found at the end of this message,
starting firefox from the command line in a script(1) session, restoring the previous
session with two tabs (twitter and facebook), refreshing twitter by clicking the logo,
and then swithcing to the facebook tab, clicking the logo there and clicking a friend's
icon (right-hand side of the window) to start a facebook chat session. The last action
in all cases caused Firefox to crash.

Unless something unexpected turns up, I can do some more testing tonight based on input
from this thread.

Anyway, last night's log:

First, with staff's :stacksize-cur=16M:

Script started on Mon Mar 13 22:35:11 2017
[Mon Mar 13 22:35:11] peter@elke:~$ firefox &
[1] 55873
[Mon Mar 13 22:35:16] peter@elke:~$ firefox:/usr/local/lib/libicuuc.so.12.0: /usr/local/lib/libicudata.so.12.0 : WARNING: symbol(icudt58_dat) size mismatch, relink your program
console.info: 2017-03-13T21:35:18.830Z: Starting AdBlocker ultimate addon...
console.info: 2017-03-13T21:35:18.833Z: Initializing webRequest...
console.info: 2017-03-13T21:35:18.836Z: Collapse style registered successfully
console.info: 2017-03-13T21:35:18.837Z: Selector style registered successfully
console.info: 2017-03-13T21:35:19.068Z: Groups metadata loaded
console.info: 2017-03-13T21:35:19.126Z: Filters metadata loaded
console.info: 2017-03-13T21:35:19.130Z: Starting loading filter rules from the storage
console.info: 2017-03-13T21:35:19.418Z: Finished loading filter rules from the storage in 287 ms
console.info: 2017-03-13T21:35:19.418Z: Starting request filter initialization
console.info: 2017-03-13T21:35:24.524Z: Finished request filter initialization in 5106 ms. Rules count: 67231
firefox:/usr/local/lib/libicuuc.so.12.0: /usr/local/lib/libicudata.so.12.0 : WARNING: symbol(icudt58_dat) size mismatch, relink your program
out of memory: 0x0000000000000048 bytes requested
[Child 15017] ###!!! ABORT: Aborting on channel error.: file /usr/obj/ports/firefox-52.0/firefox-52.0/ipc/glue/MessageChannel.cpp, line 2143
[Child 15017] ###!!! ABORT: Aborting on channel error.: file /usr/obj/ports/firefox-52.0/firefox-52.0/ipc/glue/MessageChannel.cpp, line 2143

[1]+  Segmentation fault      (core dumped) firefox
[Mon Mar 13 22:36:19] peter@elke:~$ exit

Script done on Mon Mar 13 22:36:21 2017

-------
Then upping to :stacksize-cur=32M:

Script started on Mon Mar 13 22:38:43 2017
[Mon Mar 13 22:38:43] peter@elke:~$ (reverse-i-search)`': f': doas mg /etc/login.conf (reverse-i-search)`fi': cat firefoxlog.txt [1@r': cat [1@e': cat script firefoxlog.txtfirefox & [10@[Mon Mar 13 22:38:43] peter@elke:~$
[1] 89749
[Mon Mar 13 22:38:49] peter@elke:~$ firefox:/usr/local/lib/libicuuc.so.12.0: /usr/local/lib/libicudata.so.12.0 : WARNING: symbol(icudt58_dat) size mismatch, relink your program
console.info: 2017-03-13T21:38:52.025Z: Starting AdBlocker ultimate addon...
console.info: 2017-03-13T21:38:52.027Z: Initializing webRequest...
console.info: 2017-03-13T21:38:52.030Z: Collapse style registered successfully
console.info: 2017-03-13T21:38:52.031Z: Selector style registered successfully
console.info: 2017-03-13T21:38:52.326Z: Groups metadata loaded
console.info: 2017-03-13T21:38:52.384Z: Filters metadata loaded
console.info: 2017-03-13T21:38:52.388Z: Starting loading filter rules from the storage
console.info: 2017-03-13T21:38:52.664Z: Finished loading filter rules from the storage in 276 ms
console.info: 2017-03-13T21:38:52.664Z: Starting request filter initialization
console.info: 2017-03-13T21:38:55.417Z: Finished request filter initialization in 2753 ms. Rules count: 67231
ATTENTION: default value of option force_s3tc_enable overridden by environment.
1489441162359   addons.update-checker   WARN    Update manifest for {972ce4c6-7e08-4474-a285-3208198ce6fd} did not contain an updates property
1489441162469   addons.update-checker   WARN    Update manifest for [hidden email] did not contain an updates property
1489441162483   addons.update-checker   WARN    Update manifest for [hidden email] did not contain an updates property
1489441162497   addons.update-checker   WARN    Update manifest for [hidden email] did not contain an updates property
1489441162511   addons.update-checker   WARN    Update manifest for [hidden email] did not contain an updates property
out of memory: 0x0000000000002000 bytes requested

[1]+  Segmentation fault      (core dumped) firefox
[Mon Mar 13 22:40:46] peter@elke:~$ exit

Script done on Mon Mar 13 22:40:52 2017

-------
next up, :stacksize-cur=48M:


Script started on Mon Mar 13 22:46:36 2017
[Mon Mar 13 22:46:36] peter@elke:~$ (reverse-i-search)`': &': firefox & [13@[Mon Mar 13 22:46:36] peter@elke:~$ firefox
[1] 39818
[Mon Mar 13 22:46:42] peter@elke:~$ firefox:/usr/local/lib/libicuuc.so.12.0: /usr/local/lib/libicudata.so.12.0 : WARNING: symbol(icudt58_dat) size mismatch, relink your program
console.info: 2017-03-13T21:46:44.884Z: Starting AdBlocker ultimate addon...
console.info: 2017-03-13T21:46:44.886Z: Initializing webRequest...
console.info: 2017-03-13T21:46:44.889Z: Collapse style registered successfully
console.info: 2017-03-13T21:46:44.890Z: Selector style registered successfully
console.info: 2017-03-13T21:46:45.115Z: Groups metadata loaded
console.info: 2017-03-13T21:46:45.172Z: Filters metadata loaded
console.info: 2017-03-13T21:46:45.175Z: Starting loading filter rules from the storage
console.info: 2017-03-13T21:46:45.474Z: Finished loading filter rules from the storage in 299 ms
console.info: 2017-03-13T21:46:45.474Z: Starting request filter initialization
console.info: 2017-03-13T21:46:48.449Z: Finished request filter initialization in 2974 ms. Rules count: 67231
ATTENTION: default value of option force_s3tc_enable overridden by environment.
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: Failed 2 buffer db=0 dw=0 for 0, 0, 1907, 932 (t=105.615) [GFX1-]: Failed 2 buffer db=0 dw=0 for 0, 0, 1907, 932
out of memory: 0x0000000000002000 bytes requested

[1]+  Segmentation fault      (core dumped) firefox
[Mon Mar 13 22:48:40] peter@elke:~$ exit

Script done on Mon Mar 13 22:48:43 2017

---------
then :stacksize-cur=64M:

Script started on Mon Mar 13 22:56:30 2017
[Mon Mar 13 22:56:30] peter@elke:~$ (reverse-i-search)`': &': firefox & [13@[Mon Mar 13 22:56:30] peter@elke:~$ firefox
[1] 82988
[Mon Mar 13 22:56:35] peter@elke:~$ firefox:/usr/local/lib/libicuuc.so.12.0: /usr/local/lib/libicudata.so.12.0 : WARNING: symbol(icudt58_dat) size mismatch, relink your program
console.info: 2017-03-13T21:56:37.896Z: Starting AdBlocker ultimate addon...
console.info: 2017-03-13T21:56:37.898Z: Initializing webRequest...
console.info: 2017-03-13T21:56:37.902Z: Collapse style registered successfully
console.info: 2017-03-13T21:56:37.904Z: Selector style registered successfully
console.info: 2017-03-13T21:56:38.195Z: Groups metadata loaded
console.info: 2017-03-13T21:56:38.256Z: Filters metadata loaded
console.info: 2017-03-13T21:56:38.260Z: Starting loading filter rules from the storage
console.info: 2017-03-13T21:56:38.612Z: Finished loading filter rules from the storage in 352 ms
console.info: 2017-03-13T21:56:38.613Z: Starting request filter initialization
console.info: 2017-03-13T21:56:44.548Z: Finished request filter initialization in 5935 ms. Rules count: 67231
ATTENTION: default value of option force_s3tc_enable overridden by environment.
out of memory: 0x0000000000008000 bytes requested

[1]+  Segmentation fault      (core dumped) firefox
[Mon Mar 13 22:57:11] peter@elke:~$ exit

Script done on Mon Mar 13 22:57:13 2017

---------
going to :stacksize-cur=128M:

Script started on Mon Mar 13 22:58:40 2017
[Mon Mar 13 22:58:40] peter@elke:~$ (reverse-i-search)`': &': firefox & [13@[Mon Mar 13 22:58:40] peter@elke:~$ firefox
[1] 93889
[Mon Mar 13 22:58:44] peter@elke:~$ firefox:/usr/local/lib/libicuuc.so.12.0: /usr/local/lib/libicudata.so.12.0 : WARNING: symbol(icudt58_dat) size mismatch, relink your program
console.info: 2017-03-13T21:58:46.587Z: Starting AdBlocker ultimate addon...
console.info: 2017-03-13T21:58:46.590Z: Initializing webRequest...
console.info: 2017-03-13T21:58:46.592Z: Collapse style registered successfully
console.info: 2017-03-13T21:58:46.594Z: Selector style registered successfully
console.info: 2017-03-13T21:58:46.822Z: Groups metadata loaded
console.info: 2017-03-13T21:58:46.877Z: Filters metadata loaded
console.info: 2017-03-13T21:58:46.880Z: Starting loading filter rules from the storage
console.info: 2017-03-13T21:58:47.458Z: Finished loading filter rules from the storage in 578 ms
console.info: 2017-03-13T21:58:47.459Z: Starting request filter initialization
console.info: 2017-03-13T21:58:50.098Z: Finished request filter initialization in 2639 ms. Rules count: 67231
ATTENTION: default value of option force_s3tc_enable overridden by environment.
Assertion failure: addr == p, at /usr/obj/ports/firefox-52.0/firefox-52.0/js/src/jit/ProcessExecutableMemory.cpp:322

[1]+  Segmentation fault      (core dumped) firefox
[Mon Mar 13 22:59:31] peter@elke:~$ exit

Script done on Mon Mar 13 22:59:33 2017

---------
doubling again :stacksize-cur=256M:

Script started on Mon Mar 13 23:05:24 2017
[Mon Mar 13 23:05:24] peter@elke:~$ (reverse-i-search)`': &': firefox & [13@[Mon Mar 13 23:05:24] peter@elke:~$ firefox
[1] 15432
[Mon Mar 13 23:05:28] peter@elke:~$ firefox:/usr/local/lib/libicuuc.so.12.0: /usr/local/lib/libicudata.so.12.0 : WARNING: symbol(icudt58_dat) size mismatch, relink your program
console.info: 2017-03-13T22:05:31.017Z: Starting AdBlocker ultimate addon...
console.info: 2017-03-13T22:05:31.019Z: Initializing webRequest...
console.info: 2017-03-13T22:05:31.022Z: Collapse style registered successfully
console.info: 2017-03-13T22:05:31.023Z: Selector style registered successfully
console.info: 2017-03-13T22:05:31.249Z: Groups metadata loaded
console.info: 2017-03-13T22:05:31.303Z: Filters metadata loaded
console.info: 2017-03-13T22:05:31.306Z: Starting loading filter rules from the storage
console.info: 2017-03-13T22:05:31.807Z: Finished loading filter rules from the storage in 501 ms
console.info: 2017-03-13T22:05:31.809Z: Starting request filter initialization
console.info: 2017-03-13T22:05:35.731Z: Finished request filter initialization in 3923 ms. Rules count: 67231
ATTENTION: default value of option force_s3tc_enable overridden by environment.
out of memory: 0x0000000000000080 bytes requested

[1]+  Segmentation fault      (core dumped) firefox
[Mon Mar 13 23:06:36] peter@elke:~$ exit

Script done on Mon Mar 13 23:06:37 2017

the dmesg:  

OpenBSD 6.1-beta (GENERIC.MP) #12: Mon Mar 13 10:09:44 MDT 2017
    [hidden email]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 17046183936 (16256MB)
avail mem = 16524894208 (15759MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeb500 (35 entries)
bios0: vendor American Megatrends Inc. version "4.6.5" date 11/21/2013
bios0: Notebook W840SU Series
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC FPDT ASF! SSDT SSDT SSDT MCFG HPET SSDT SSDT DMAR CSRT
acpi0: wakeup devices PXSX(S4) RP01(S4) PXSX(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) GLAN(S4) EHC1(S3) EHC2(S3) XHC_(S3) HDEF(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz, 2594.31 MHz
cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 2594313340 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz, 2593.99 MHz
cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz, 2593.99 MHz
cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz, 2593.99 MHz
cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec00000, version 20, 40 pins
acpimcfg0 at acpi0 addr 0xf8000000, bus 0-63
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus 2 (RP03)
acpiprt3 at acpi0: bus 3 (RP04)
acpiprt4 at acpi0: bus -1 (P0P2)
acpiprt5 at acpi0: bus -1 (P0PA)
acpiprt6 at acpi0: bus -1 (P0PB)
acpiprt7 at acpi0: bus -1 (PEG0)
acpiprt8 at acpi0: bus -1 (PEG1)
acpiprt9 at acpi0: bus -1 (PEG2)
acpiec0 at acpi0
acpicpu0 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpicpu1 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpicpu2 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpicpu3 at acpi0: C3(200@506 mwait.1@0x60), C2(200@148 mwait.1@0x33), C1(1000@1 mwait.1), PSS
acpitz0 at acpi0: critical temperature is 120 degC
"INT3F0D" at acpi0 not configured
"MSFT0001" at acpi0 not configured
"ETD0403" at acpi0 not configured
"PNPC000" at acpi0 not configured
acpibtn0 at acpi0: PWRB
acpibtn1 at acpi0: SLPB
acpibtn2 at acpi0: LID0
acpiac0 at acpi0: AC unit online
acpibat0 at acpi0: BAT0 model "BAT" serial 0001 type LION oem "Notebook"
"PNP0C14" at acpi0 not configured
"INT340E" at acpi0 not configured
acpivideo0 at acpi0: GFX0
acpivout0 at acpivideo0: DD1F
cpu0: Enhanced SpeedStep 2594 MHz: speeds: 2601, 2600, 2500, 2300, 2200, 2000, 1900, 1800, 1600, 1500, 1400, 1200, 1100, 1000, 800, 754 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x0b
inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics" rev 0x0b
drm0 at inteldrm0
inteldrm0: msi
inteldrm0: 1920x1080, 32bpp
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
azalia0 at pci0 dev 3 function 0 "Intel Core 4G HD Audio" rev 0x0b: msi
xhci0 at pci0 dev 20 function 0 "Intel 8 Series xHCI" rev 0x04: msi
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 addr 1
"Intel 8 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured
azalia1 at pci0 dev 27 function 0 "Intel 8 Series HD Audio" rev 0x04: msi
azalia1: codecs: Realtek ALC282
audio0 at azalia1
ppb0 at pci0 dev 28 function 0 "Intel 8 Series PCIE" rev 0xe4: msi
pci1 at ppb0 bus 1
ppb1 at pci0 dev 28 function 2 "Intel 8 Series PCIE" rev 0xe4: msi
pci2 at ppb1 bus 2
iwm0 at pci2 dev 0 function 0 "Intel Dual Band Wireless AC 7260" rev 0x73, msi
ppb2 at pci0 dev 28 function 3 "Intel 8 Series PCIE" rev 0xe4: msi
pci3 at ppb2 bus 3
rtsx0 at pci3 dev 0 function 0 "Realtek RTL8411B Card Reader" rev 0x01: msi
sdmmc0 at rtsx0: 4-bit
re0 at pci3 dev 0 function 1 "Realtek 8168" rev 0x12: RTL8411B (0x5c80), msi, address 80:fa:5b:06:1f:f7
rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0
ehci0 at pci0 dev 29 function 0 "Intel 8 Series USB" rev 0x04: apic 2 int 23
usb1 at ehci0: USB revision 2.0
uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
pcib0 at pci0 dev 31 function 0 "Intel 8 Series LPC" rev 0x04
ahci0 at pci0 dev 31 function 2 "Intel 8 Series AHCI" rev 0x04: msi, AHCI 1.3
ahci0: port 0: 6.0Gb/s
ahci0: port 1: 6.0Gb/s
scsibus1 at ahci0: 32 targets
sd0 at scsibus1 targ 0 lun 0: <ATA, Samsung SSD 850, EXM0> SCSI3 0/direct fixed naa.500253884019088e
sd0: 976762MB, 512 bytes/sector, 2000409264 sectors, thin
sd1 at scsibus1 targ 1 lun 0: <ATA, Crucial_CT240M50, MU05> SCSI3 0/direct fixed naa.500a07510c250249
sd1: 228936MB, 512 bytes/sector, 468862128 sectors, thin
ichiic0 at pci0 dev 31 function 3 "Intel 8 Series SMBus" rev 0x04: apic 2 int 18
iic0 at ichiic0
spdmem0 at iic0 addr 0x50: 8GB DDR3 SDRAM PC3-12800 SO-DIMM
spdmem1 at iic0 addr 0x52: 8GB DDR3 SDRAM PC3-12800 SO-DIMM
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
vmm0 at mainbus0: VMX/EPT
error: [drm:pid0:intel_uncore_check_errors] *ERROR* Unclaimed register before interrupt
uhidev0 at uhub0 port 4 configuration 1 interface 0 "eGalax Inc. eGalaxTouch EXC7910-1057-13.00.00" rev 2.00/57.01 addr 2
uhidev0: iclass 3/1, 7 report ids
uhid0 at uhidev0 reportid 3: input=63, output=63, feature=0
uhid1 at uhidev0 reportid 5: input=0, output=0, feature=2
ums0 at uhidev0 reportid 6: 1 button, tip
wsmouse1 at ums0 mux 0
ums1 at uhidev0 reportid 7
ums1: mouse has no X report
ugen0 at uhub0 port 5 "Intel product 0x07dc" rev 2.00/0.01 addr 3
uvideo0 at uhub0 port 6 configuration 1 interface 0 "Generic BisonCam, NB Pro" rev 2.00/6.07 addr 4
video0 at uvideo0
uhub2 at uhub1 port 1 configuration 1 interface 0 "Intel Rate Matching Hub" rev 2.00/0.04 addr 2
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on sd1a (fe9b028d3772f310.a) swap on sd1b dump on sd1b
iwm0: hw rev 0x140, fw ver 16.242414.0, address a0:a8:cd:63:ab:b9

--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: firefox 52 - crashes at startup or later due to oom

Landry Breuil-5
In reply to this post by Sebastien Marie-3
On Tue, Mar 14, 2017 at 11:21:02AM +0100, Sebastien Marie wrote:

> On Tue, Mar 14, 2017 at 10:28:05AM +0100, Landry Breuil wrote:
> > You can't sanely run a desktop session with any browser using the
> > default limits anyway...
>
> I disagree. I run firefox with low memory pressure:
>
> 97871 semarie    2    0  434M  320M sleep/1   poll     34:42  0.68% firefox
> 95072 semarie    2    0  338M  260M sleep/1   poll     27:04  0.34% firefox
>
> (with two processes due to e10n).
>
> My session has 12 tabs opened with 3 or 4 tabs javascript enabled. But I
> agree my use of firefox isn't representative of common use-case (no
> videos or other ressources consuming websites).
>
> The running process is firefox-52.0 patched for allocating 128 Mo for
> javascript (instead of 1 Go).

Ppl who dont like the current situation of having to either patch or
raise your ulimits can propose constructive ideas on
https://bugzilla.mozilla.org/show_bug.cgi?id=1347139 - with my limited
time and interest into that never-ending problem of 'web browsers are
piles of shitttons of code not designed with security in mind' (that
personally not my pov), that's all i can do for now.

Landry

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: firefox 52 - crashes at startup or later due to oom

Diogo Galvao
In reply to this post by Sebastien Marie-3
On Tue, Mar 14, 2017 at 2:42 AM, Sebastien Marie <[hidden email]> wrote:
>
> Personally, what bother me is the fact that datastack limit is the same
> for all processes, without convenient way (for my knowledge) to run some
> programs with alternate class (and bigger datastack).
> ...
> If people have others suggestions, I would be glad to hear them :)

Why not running Firefox as a different user? Then you can also assign
another login class to it.

I've been trying this as an attempt to separate privileges and got used
to it quite quickly. The biggest annoyance is during file uploads, since
it intentionally can't read my files.

This idea might be worse than your doas su approach, but if you're
inclined to it, use xauth to generate an .Xauthority file then just doas
accordingly. I actually have a crude script for automating this that I
could share, in case you or anyone are interested.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: firefox 52 - crashes at startup or later due to oom

Daniel Jakots-3
In reply to this post by Sebastien Marie-3
On Mon, 13 Mar 2017 06:34:12 +0100, Sebastien Marie <[hidden email]>
wrote:

> Alternatively, I would be glad if someone could test the diff below

I've tested it during this afternoon. It worked without any problem.
"Production-critical use case" like youtube worked fine (though it's
firefox not chrome) :>

Diff looks sensible to me, ok danj@ if you want to commit it Landry.

Loading...