Date: Mon, 02 Jan 2023 11:51:08 +0000 From: bugzilla-noreply@freebsd.org To: pkg@FreeBSD.org Subject: [Bug 268711] ports-mgmt/pkg pkg-update(8) and Electron-based applications fail when /tmp is from tmpmfs="YES" in rc.conf(5) Message-ID: <bug-268711-32340-9uCbaB3IPh@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-268711-32340@https.bugs.freebsd.org/bugzilla/> References: <bug-268711-32340@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268711 --- Comment #4 from Graham Perrin <grahamperrin@freebsd.org> --- Created attachment 239207 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D239207&action= =3Dedit Screenshot: Chromium: Can't open this page chrome://newtab Second tab > Can't open this page >=20 > =E2=80=A6 >=20 > Error code: 5 =E2=80=A6 and so on. All new tabs failed.=20 In most cases, split-second visible appearance of new tab content (e.g. the Google search page) is followed by disappearance with a snap (5) or can't o= pen (5).=20 In other cases, I could not observe any new tab content before the error co= de appeared. Maybe appearance and disappearance occurred too fast for my eye to see.=20 Sometimes: a click on the 'Reload' button was followed by unexpected closur= e of the window (all tabs).=20 I don't recall as many closures as are logged below, so I guess that each e= xit on signal 5 (a crash?) was for a chrome://newtab failure.=20 root@fuji:~ # zgrep chrome /var/log/messages.0.bz2 root@fuji:~ # grep chrome /var/log/messages Jan 2 11:14:17 fuji kernel: pid 1190 (chrome), jid 0, uid 1001: exited on signal 5 Jan 2 11:15:13 fuji kernel: pid 1211 (chrome), jid 0, uid 1001: exited on signal 5 Jan 2 11:15:18 fuji kernel: pid 1213 (chrome), jid 0, uid 1001: exited on signal 5 Jan 2 11:15:27 fuji kernel: pid 1215 (chrome), jid 0, uid 1001: exited on signal 5 Jan 2 11:15:38 fuji kernel: pid 1217 (chrome), jid 0, uid 1001: exited on signal 5 Jan 2 11:15:44 fuji kernel: pid 1174 (chrome), jid 0, uid 1001: exited on signal 5 Jan 2 11:15:51 fuji kernel: pid 1226 (chrome), jid 0, uid 1001: exited on signal 5 Jan 2 11:16:00 fuji kernel: pid 1243 (chrome), jid 0, uid 1001: exited on signal 5 Jan 2 11:17:03 fuji kernel: pid 1247 (chrome), jid 0, uid 1001: exited on signal 5 Jan 2 11:17:11 fuji kernel: pid 1249 (chrome), jid 0, uid 1001: exited on signal 5 Jan 2 11:17:32 fuji kernel: pid 1220 (chrome), jid 0, uid 1001: exited on signal 5 Jan 2 11:17:50 fuji kernel: pid 1272 (chrome), jid 0, uid 1001: exited on signal 5 Jan 2 11:17:56 fuji kernel: pid 1278 (chrome), jid 0, uid 1001: exited on signal 5 Jan 2 11:18:00 fuji kernel: pid 1280 (chrome), jid 0, uid 1001: exited on signal 5 Jan 2 11:18:04 fuji kernel: pid 1283 (chrome), jid 0, uid 1001: exited on signal 5 Jan 2 11:18:07 fuji kernel: pid 1285 (chrome), jid 0, uid 1001: exited on signal 5 Jan 2 11:18:09 fuji kernel: pid 1287 (chrome), jid 0, uid 1001: exited on signal 5 Jan 2 11:18:11 fuji kernel: pid 1291 (chrome), jid 0, uid 1001: exited on signal 5 Jan 2 11:18:13 fuji kernel: pid 1293 (chrome), jid 0, uid 1001: exited on signal 5 root@fuji:~ #=20 ---- Workaround: cease using tmpmfs. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-268711-32340-9uCbaB3IPh>