Chrome.exe crash with memory leak
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Chrome found crashed every morning for past couple of weeks (Nov'17) + "not enough resources to run chrome.exe". Experiments with disabled extensions reveal connection to Vimium.
Steps:
- open https://www.rx7club.com/suspension-wheels-tires-brakes-20/how-read-shock-dyno-721655/
- watch Chrome's TaskManager (Memory and JavaScriptMemory) for a few minutes
Result:
- without Vimium memory is not growing (being reset to same numbers every ~20secs)
- with Vimium memory grows, which possibly leads to Chrome.exe crash in case of dozen open Tabs
OS: Win10Pro 17.03 (15063.726) 64-bit
Chrome: Version 62.0.3202.94 (Official Build) (64-bit)
Vimium: 1.61.1 (non-default settings)
Contributor guide
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
No source file or test is named. First reproduce the leak with Vimium enabled and disabled on the linked page using Chrome Task Manager, then compare the extension's behavior while memory and JavaScript memory grow. Done means identifying and fixing the Vimium-related growth and confirming memory remains stable across repeated checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100