Running FreeBSD 13.0-RELEASE-p11. Iridium doesn't start. Crashes immediately with a trace trap upon launching. No idea why. "[1] 32142 trace trap iridium" is the only output I get, nothing else. That 5 digit number after "[1]" changes every time I execute Iridium.
(In reply to Jeremy Passarelli from comment #0) Please provide more information, like your dmesg, ulimit -a. Please also run iridium with --enable-logging=stderr --v=1 and attach the output to the ticket.
Iridium works fine on my FreeBSD 13 MATE VMware VM on my main Windows 10 install. On my FreeBSD 13 Xfce VMware VM, this trace trap occurs. Will provide the requested info in another comment.
iridium --enable-logging=stderr --v=1: [19901:258023424:0430/103115.874006:VERBOSE1:sandbox_freebsd.cc(165)] SandboxLinux::InitializeSandbox: process_type= sandbox_type=Unsandboxed [1] 19901 trace trap iridium --enable-logging=stderr --v=1 ulimit -a: -t: cpu time (seconds) unlimited -f: file size (blocks) unlimited -d: data seg size (kbytes) 33554432 -s: stack size (kbytes) 524288 -c: core file size (blocks) unlimited -m: resident set size (kbytes) unlimited -l: locked-in-memory size (kbytes) 131072 -u: processes 6656 -n: file descriptors 57654 -b: socket buffer size (bytes) unlimited -v: virtual memory size (kbytes) unlimited -p: pseudo-terminals unlimited -w: swap size (kbytes) unlimited -k: kqueues unlimited -o: umtx shared locks unlimited dmesg: https://pastebin.com/Ls4FtxF6
I have quite the same error on FreeBSD 13.2-p4 running in VirtualBox 7.0.12 hosted on Windows machine: ❯ iridium Trace/BPT trap pkg install www/iridium from the latest branch.
dmesg says pid 2616 (iridium), jid 0, uid 1001: exited on signal 5 ❯ ulimit -a number of pseudoterminals (-P) unlimited socket buffer size (bytes, -b) unlimited core file size (blocks, -c) unlimited data seg size (kbytes, -d) 33554432 file size (blocks, -f) unlimited max kqueues (-k) unlimited max locked memory (kbytes, -l) 131072 max memory size (kbytes, -m) unlimited open files (-n) 688824 pipe size (512 bytes, -p) 1 stack size (kbytes, -s) 524288 cpu time (seconds, -t) unlimited max user processes (-u) 26370 virtual memory (kbytes, -v) unlimited swap size (kbytes, -w) unlimited ❯ iridium --enable-logging=stderr --v=1 [6301:803356672:1030/085325.578846:WARNING:chrome_main_delegate.cc(613)] This is Chrome version 118.0.5993.70 (not a warning) [6301:803356672:1030/085325.579521:INFO:cpu_info.cc(53)] Available number of cores: 4 [6301:803356672:1030/085325.579720:VERBOSE1:sandbox_freebsd.cc(158)] SandboxLinux::InitializeSandbox: process_type= sandbox_type=Unsandboxed [6301:803356672:1030/085325.608900:WARNING:policy_logger.cc(148)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(88) Could not create policy manager as CBCM is not enabled. [6301:803356672:1030/085325.612700:VERBOSE1:variations_field_trial_creator_base.cc(493)] Applying FieldTrialTestingConfig [6301:803356672:1030/085325.612965:VERBOSE1:variations_field_trial_creator_base.cc(322)] VariationsSetupComplete [6301:803356672:1030/085325.864163:VERBOSE1:webrtc_event_log_manager.cc(97)] WebRTC remote-bound event logging enabled. Trace/BPT trap
Now I see the same problem on real hardware (old laptop) running FreeBSD 14.
Duplicate of bug 272221? Try running as "proccontrol -m wxmap iridium"