hyper: Hyper crashing since update to 1.4.x

I’m experiencing crashes as well while running npm install for a medium/large app. OS and Hyper versions the same as above with no plugins either. Right before the crash, the npm process shot up to 127% CPU in Activity Monitor.

From the crash report:

Crashed Thread:        0  CrBrowserMain  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [0]

Let me know if I can provide any more information to help, it’s consistently crashing.

We had a confirmation on twitter by @tylersticka but we need more to consider this issue fixed 😄

I clicked “show details” this time, putting those into this gist so it doesn’t dominate the thread: https://gist.github.com/tylersticka/0958e7958a5e53828d3980cdff23e7b6

Disabling hyperline seems to have done the trick, thanks for the tip @albinekb 😄

Updated to v1.4.3 and issues appear to be resolved. Running smoothly! Thanks

UPDATE: Hyper is crashing for me again when doing intensive tasks such as running multiple Node servers and doing yarn install

No more crashes since v1.4.6. I’ve tested on multiple projects, with all commands that used to make Hyper crash and now I have no issues.

Confirmed here. I could reliably get Hyper to crash every time I ran npm i with a project I’m working on. That crashing is gone in 1.4.6.

Please try our last v1.4.6 release. It could fix this issue definitely 🤞

@jd20 i haven’t been able to reproduce since I restarted but i’ll keep an eye out

Been running various tasks for ~ 2 hours and no crash so far. I didn’t do anything but update the app normally, plugins and stuff are as they were.

I’ll keep you posted if things take a sour turn. Thanks to the dev team for progress made so far, using a different Terminal app for a few days really made me miss Hyper. 🙂

I was having same _fastCStringContents crashes when running yarn, and 1.4.4 appears to fix.

@johnryan Try removing all plugins, then restart your system, and try to reproduce again (I use something like react-native init hypercrash && cd hypercrash && yarn). When I initially upgraded to 1.4.4, I was still getting a lot of crashes, but after putting my system into a clean state (restart everything, no plugins, etc…) I’m completely unable to reproduce anymore. So I think 1.4.4 did fix the issue. (I’m on macOS 10.12.6 btw)

@chabou just updated and ran yarn got the crash objc_msgSend() selector name: _fastCStringContents

note: it didn’t crash the second time i tried

@mattlewis92 try without plugins, especially hyperline (it runs a lot of commands in the background, and has been a problem for others)

Without writing what crashes, how it crashes and steps to reproduce with OS version, i will remove your “+1” comments. They do not help us in any way shape or form. @Sly777 @revelt @ouchxp