Date: Sat, 09 Sep 2023 00:27:21 +0000 From: bugzilla-noreply@freebsd.org To: gecko@FreeBSD.org Subject: [Bug 273291] www/firefox: Crashes on start after upgrading from 116.0.3_1,2 to 117.0,2 Message-ID: <bug-273291-21738-MxFbIukhAZ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-273291-21738@https.bugs.freebsd.org/bugzilla/> References: <bug-273291-21738@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=3D273291 --- Comment #20 from Tomoaki AOKI <junchoon@dec.sakura.ne.jp> --- And as appears in the 3rd backtrace uploaded, `c` also fails. Maybe we should set so-called breakpoint somewhere firefox starts generating core, but I'm not enough understood how and where to set it. :-( Enabling DEBUG option needed? But in some cases, especially in race conditi= ons, setting it could cause problems dissapear, with the cost of larger binary a= nd slowness. % lldb -o r -- /usr/local/bin/firefox --ProfileManager --no-remote --private-window (lldb) target create "/usr/local/bin/firefox" Current executable set to '/usr/local/bin/firefox' (x86_64). (lldb) settings set -- target.run-args "--ProfileManager" "--no-remote" "--private-window" (lldb) r JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error: Can't find profile directory. Process 21967 exited with status =3D -1 (0xffffffff) lost connection Process 21967 launched: '/usr/local/bin/firefox' (x86_64) (lldb) c error: Process must be launched. (lldb) q --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273291-21738-MxFbIukhAZ>