macOS 27: Chrome for Testing 148 aborts on launch (SIGABRT); pup falls back to Chrome but the user sees an app start and quit on every window

by adom

pup gives your AI a real browser on your desktop that it drives completely, in the background, signed in as you: windows that never jump in front of your work, one shared profile that learns your logins, and every window labeled on the taskbar with its AI thread's name.

Overview Files Skills Discover Packages Releases Dependencies Issues17 Breadcrumbs Pull Requests1 Activity

Open general

Joe Rouvier · 9d ago

On macOS 27.0.1 (26A434, Apple silicon), pup's pinned default browser, Chrome for Testing 148.0.7778.97, aborts as soon as it is launched:

Install: ~/.cache/puppeteer/chrome/mac_arm-148.0.7778.97/chrome-mac-arm64/Google Chrome for Testing.app, the only Chrome for Testing in the cache.
Crash reports: ~/Library/Logs/DiagnosticReports/Google Chrome for Testing-*.ips, EXC_CRASH / SIGABRT ("Abort trap: 6"). The parent process is node, pup's bridge. There is one report per pup_open_window, from 11:14 to 23:46 on 2026-11-01.
pup then falls back to the installed Google Chrome, so the window does open. But on every open the user sees an app start in the Dock and quit at once, and reported it as an app "launching and then immediately exiting".

Workaround that stopped it: pup_use {"browser": "chrome"} (pinned system Chrome). pup_readiness still reports Chrome for Testing as the pinned default until then.

Suggested fix: when the cached Chrome for Testing fails its first launch on a host, mark it unusable there and default to system Chrome, or say so in pup_readiness, rather than relaunching it on every window.

1 Reply

Kyle Bergstedt · 7d ago

Thanks Joe, and thanks John for the pup-side fix. On the Mac build side: we're reproducing the Chrome for Testing 148 abort on macOS 27, then pinning a Chrome for Testing build that launches on 27 for the Mac pup, and testing it on a real macOS 27 machine before it ships. Until then pup falls back to your Chrome, so it keeps working, just with the start-and-quit flicker you described. Updates here.