[Bug 272221] www/chromium error "V8 javascript OOM"
- Reply: bugzilla-noreply_a_freebsd.org: "maintainer-feedback requested: [Bug 272221] www/chromium error "V8 javascript OOM""
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 272221] www/chromium error "V8 javascript OOM""
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 272221] www/chromium error "V8 javascript OOM""
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 272221] www/chromium error "V8 javascript OOM""
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 272221] www/chromium error "V8 javascript OOM""
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 272221] www/chromium error "V8 javascript OOM""
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 26 Jun 2023 11:07:40 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272221 Bug ID: 272221 Summary: www/chromium error "V8 javascript OOM" Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: chromium@FreeBSD.org Reporter: pmc@citylink.dinoex.sub.org Assignee: chromium@FreeBSD.org Flags: maintainer-feedback?(chromium@FreeBSD.org) Fresh install from source 2023Q2 (i.e. chromium-113.0.5672.126) on 13.2-RELEASE-p1; machine i5-3570T, 8 GM mem chromium fails on practically every page load with "Aw, Snap! Error Code 5". It fails with the same error on chrome://settings/ It does, however, display plain HTML pages correctly. Messages in the terminal: chrome://settings/ <--- Last few GCs ---> [44673:0x1a55086abc80] 183 ms: Mark-Compact (reduce) 1.5 (3.7) -> 1.5 (2.7) MB, 2.37 / 0.00 ms (average mu = 0.020, current mu = 0.020) last resort; GC in old space requested [44673:0x1a55086abc80] 185 ms: Mark-Compact (reduce) 1.5 (2.7) -> 1.5 (2.7) MB, 2.50 / 0.00 ms (average mu = 0.014, current mu = 0.008) last resort; GC in old space requested <--- JS stacktrace ---> [44673:1469513728:0626/125245.139319:ERROR:v8_initializer.cc(752)] V8 javascript OOM (CALL_AND_RETRY_LAST). There should not be any memory constraints in place, and running as root shows the same behaviour. Options : ALSA : off CODECS : on CUPS : on DEBUG : off DRIVER : on HEIMDAL : off HEIMDAL_BASE : on KERBEROS : on LTO : off MIT : off PULSEAUDIO : off SNDIO : on TEST : off Workaround found: $ chrome --js-flags=--lite-mode -- You are receiving this mail because: You are the assignee for the bug.