Memory usage (Windows 10)
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 1703 build 15063
-
Hyper.app version: v3.0.0 canary 8
-
Link of a Gist with the contents of your .hyper.js: https://gist.github.com/willstocks-tech/d534245ba7cf3ce8e5f09ec3022e5d46
-
Relevant information from devtools (CMD+ALT+I on macOS, CTRL+SHIFT+I elsewhere): N/A
-
The issue is reproducible in vanilla Hyper.app: Yes, albeit slightly lessened
Issue
Hi guys,
On my Windows 10 machine, I'm seeing pretty high memory usage for the Hyper app - higher with plugins installed (obviously) but still relatively when vanilla (around 170MB), which is quite a hefty chunk on a (relatively) lower powered machine!
With plugins:

Without:

I can't find anything in devtools to indicate what's consuming the memory when the plugins are installed... is there an easy way to do this? To work out which plugin exactly is using up so much memory? The "with plugins" screenshot was about an hour after launching hyper (with the plugins installed), not doing anything and the consumption just gradually increasing.
I also keep repeatedly seeing the following notification:

Again, I can't quite work out whether this is Hyper or a plugin and it's sporadic 😞
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 reported memory growth on Windows 10 with vanilla Hyper and with the listed plugins, using the provided .hyper.js Gist and DevTools. First compare the two configurations and identify whether Hyper or a plugin accounts for the increase and recurring notification. Done means the responsible component and reproducible cause are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- desktop, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100