vercel / hyper

A terminal built on web technologies
https://hyper.is
MIT License
43.27k stars 3.52k forks source link

Hyper crashes whilst idle after update #2168

Open timothyis opened 7 years ago

timothyis commented 7 years ago

Issue

image

Here's how I got this:

Error text:

A JavaScript error occurred in the main process
Uncaught Exception:
Error: Object has been destroyed
at notify (/Applications/Hyper.app/Contents/Resources/app.asar/notify.js:36:8)
at err (/Applications/Hyper.app/Contents/Resources/app.asar/plugins.js:86:11)
at err (/Applications/Hyper.app/Contents/Resources/app.asar/plugins/install.js:43:7)
at cp.exec.err (/Applications/Hyper.app/Contents/Resources/app.asar/plugins/install.js:28:13)
at ChildProcess.exithandler (child_process.js:214:7)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at maybeClose (internal/child_process.js:885:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
chabou commented 7 years ago

My guess: Update has failed, leaving Hyper running without any window. 30mn later, hyper check for an update and found one. Want to notify but no more window.

badlands commented 7 years ago

Still happens on version 1.4.3

Here's how I got this

Launched Hyper, performed simple actions (vim, ls, ...), left it open doing nothing.

Problem Report

Process:               Hyper [21559]
Path:                  /Applications/Hyper.app/Contents/MacOS/Hyper
Identifier:            co.zeit.hyper
Version:               1.4.3 (1.4.3.88)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Hyper [21559]
User ID:               501

Date/Time:             2017-09-06 12:19:01.219 +0200
OS Version:            Mac OS X 10.12.6 (16G29)
Report Version:        12
Anonymous UUID:        F63DBDE0-0489-1986-FF76-7A0335449587

Sleep/Wake UUID:       319CB022-2990-4726-83F5-69B69DA8A22D

Time Awake Since Boot: 64000 seconds
Time Since Wake:       2800 seconds

System Integrity Protection: enabled

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

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

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

VM Regions Near 0x28694026bec0:
    Memory Tag 255         0000258f47540000-0000258f47542000 [    8K] ---/rwx SM=NUL  
--> 
    Memory Tag 255         00002982a7d00000-00002982a7d80000 [  512K] rw-/rwx SM=PRV  

Application Specific Information:
objc_msgSend() selector name: _fastCStringContents:

Thread 0 Crashed:: CrBrowserMain  Dispatch queue: com.apple.main-thread
0   libobjc.A.dylib                 0x00007fffdc75005d objc_msgSend + 29

EDIT 07.09.2017: Crashes happen more frequently when Hyper is open (idle) in a certain folder and xCode is open and building/running a project whose files are in the same exact folder.

revelt commented 7 years ago

This morning I found my Hyper crashed when left overnight. I'll be using iTerm2 from now on.

chabou commented 7 years ago

@badlands v1.4.4 just released. I hope that it will resolve your crash issue (but this not the subject of this issue) Please update https://github.com/zeit/hyper/issues/2152 if your issue is not resolved

asotog commented 7 years ago

I'm on 1.4.6 still seeing this issue happening It happens to me when i have the terminal in the background and not using it for like an hour. Also not sure if helps but i usually have a process running (for example server running in a tab).

screen shot 2017-10-02 at 2 05 59 pm

Version details: Hyper 1.4.6 (stable)

Plugins Installed:

EvanDarwin commented 6 years ago

I just encountered this issue during my first install of Hyper. Unfortunately I didn't catch the stacktrace.

Stanzilla commented 6 years ago

@EvanDarwin release or canary version?

EvanDarwin commented 6 years ago

@Stanzilla Release, when I was installing for the first time on W10 Build 16299.192

markau commented 5 years ago

I have just started getting this issue over the past two weeks or so. It occurs after locking the Windows PC for a period of time (certain to occur overnight). v2.1.2