Update: Several reproduction sessions later, it appears that the content of one specific YAML file's PSI structure is causing a negative interaction with the system's EndpointSecurity extension process. Either one of the AV products on my work machine or the EndpointSecurity extension itself are panicking when the Pasteboard daemon attempts to output the contents. My work's IT team is awesome, so they upgraded a testing machine to 26.3b2, ran the same test, and it was also affected.
The issue was happening in Ghostty, iTerm2, and Terminal.app. It happened by (a) pasting directly into the terminal prompt with Command-V, (b) using `pbpaste` in any way (like piping it into `wc -c`), or (c) pasting into an editor like Neovim with Command-V.
It doesn't happen with any other file I tested it with. It also doesn't happen if I try to paste into another app, like Visual Studio Code, TextEdit, or IntelliJ IDEA itself.
Nothing is inherently wrong with the binary/text content of the file. It's all ASCII characters.
I would normally do something like that; however, we opted to open an AppleCare Enterprise case for it, since it gets an engineer to look into the issue.
Both our Mac IT manager and I are thinking that it's the AV engine (Microsoft Defender) seeing fragments of YAML in the PSI tree and then blowing up after trying to parse the next line (which is not a truly valid YAML tree, it's a YAML tree with all the semantic details produced by IntelliJ). That in and of itself shouldn't be an issue, but I guess they weren't expecting random fragments of YAML to be copied and pasted.
We're still not sure why it only triggers in terminal emulators, though. That one is a total mystery.
Update: Several reproduction sessions later, it appears that the content of one specific YAML file's PSI structure is causing a negative interaction with the system's EndpointSecurity extension process. Either one of the AV products on my work machine or the EndpointSecurity extension itself are panicking when the Pasteboard daemon attempts to output the contents. My work's IT team is awesome, so they upgraded a testing machine to 26.3b2, ran the same test, and it was also affected.
The issue was happening in Ghostty, iTerm2, and Terminal.app. It happened by (a) pasting directly into the terminal prompt with Command-V, (b) using `pbpaste` in any way (like piping it into `wc -c`), or (c) pasting into an editor like Neovim with Command-V.
It doesn't happen with any other file I tested it with. It also doesn't happen if I try to paste into another app, like Visual Studio Code, TextEdit, or IntelliJ IDEA itself.
Nothing is inherently wrong with the binary/text content of the file. It's all ASCII characters.
The macos dev forum is very responsive to questions like these, I suggest you ask this there too https://developer.apple.com/forums/tags/macos
I would normally do something like that; however, we opted to open an AppleCare Enterprise case for it, since it gets an engineer to look into the issue.
Both our Mac IT manager and I are thinking that it's the AV engine (Microsoft Defender) seeing fragments of YAML in the PSI tree and then blowing up after trying to parse the next line (which is not a truly valid YAML tree, it's a YAML tree with all the semantic details produced by IntelliJ). That in and of itself shouldn't be an issue, but I guess they weren't expecting random fragments of YAML to be copied and pasted.
We're still not sure why it only triggers in terminal emulators, though. That one is a total mystery.