Preformace terrible after upgrade
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 44.7k
- Forks
- 3.6k
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
-
I am on the latest Hyper.app version
-
I have searched the issues of this repo and believe that this is not a duplicate
-
OS version and name: Windows 10
-
Hyper.app version: 3.1.4
-
Link of a Gist with the contents of your .hyper.js: No modifications
-
Relevant information from devtools (CMD+ALT+I on macOS, CTRL+SHIFT+I elsewhere):
-
The issue is reproducible in vanilla Hyper.app: Vanilla
Issue
The performance is terrible after upgrading. I notice this especially when I open two tabs and then on the second tab navigate through the history (press up a few times). Or when pressing Ctrl+Left to jump to the previous word in a line. The user experience is like this: Press up a few times then Ctrl+Left a few times. What I see is 1-2 seconds between history changes. At each history change I see the new text appear, then I see cursor ( "_" ) appear at the beginning of the line then slowly progress one character to the right over and over until it reaches the end of the line; then the next line of history appears and this weird animation repeats. It's as if there are a ton of animations that must play and complete before the control is returned to the user.
In other words I press: up , up , up , ctrl + Left. Then I see
history 3
h_istory 3
hi_story 3
his_tory 3
hist_ory 3
histo_ry 3
histor_y 3
history 3
history 3
history 3
history 2_
_history 2
h_istory 2
hi_story 2
etc...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the delay on Windows 10 with Hyper 3.1.4 using two tabs, command history navigation, and Ctrl+Left in an unmodified configuration. Use the described cursor animation and 1–2 second pauses as the baseline; done means history and word navigation respond without the repeated character-by-character animation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react, typescript
- Domain
- desktop, performance
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100