https://github.com/lostpebble/material-ui-potential-style-leak
https://github.com/lostpebble/material-ui-potential-style-leak
Last synced: 11 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/lostpebble/material-ui-potential-style-leak
- Owner: lostpebble
- Created: 2018-04-05T19:13:37.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2018-04-07T12:31:18.000Z (about 8 years ago)
- Last Synced: 2025-01-16T11:27:01.025Z (over 1 year ago)
- Language: TypeScript
- Size: 35.2 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
```
yarn install
```
Start our mini server
```
npm start
```
Run the "load tester" - runner that hits the server 100 times
```
npm hit-it
```
To see the memory leak you should open the url in Chrome `chrome://inspect` and go to "Open dedicated DevTools for Node".
Under the Memory tab, you can take snapshots.
* Take initial snapshot on server start
* Run `npm hit-it`
* Take another snapshot
* Run `npm hit-it` again
* Take a final snapshot
* While selecting the final snapshot, at the top change where it says "All Objects" to "Objects allocated between Snapshot 2 and Snapshot 3"
You should now see the top offenders for the memory leak are all related to styling - the `(array)` and `Object` types as well only contain styling-related data.