The default template has a memory leak #4476

Closed
dfoverdx opened this Issue May 16, 2018 · 1 comment

Comments

Projects
None yet
3 participants
@dfoverdx

dfoverdx commented May 16, 2018

Is this a bug report?

Kind of...

Did you try recovering your dependencies?

n/a

Which terms did you search for in User Guide?

n/a

Environment

Windows 10, Version 1803 (OS Build 17134.48)
Chrome Version 66.0.3359.139 (Official Build) (64-bit)
Firefox 52.7.3 (64-bit) -- I couldn't find a Chrome-equivalent Task Manager, but using Windows's Task Manager I could see that Firefox's memory usage steadily increased, and the README was the only tab open.

Steps to Reproduce

  1. In Chrome, open up https://github.com/facebook/create-react-app
  2. Press ctrl + esc to open up Chrome's Task Manager.
  3. Watch as the tab gradually takes up more and more memory.

Note: When I ran Chrome's memory profiler, I could not find where the increased memory usage was coming from. The heap remained at a constant 6.3MB, and no new allocations were detected over a span of about 20 seconds despite memory usage steadily increasing.

Expected Behavior

Memory should remain constant as it does with other github READMEs.

Actual Behavior

Memory did not remain constant; it gradually increased. Over the span of about 15 minutes, it increased to over 1 GB.

These screenshots take place over the span of roughly 2 minutes.

image

image

image

@iansu iansu changed the title from The README somehow has a memory leak to The default template has a memory leak May 18, 2018

@Timer

This comment has been minimized.

Show comment
Hide comment
@Timer

Timer May 24, 2018

Collaborator

I suspect this is a bug with webpack-dev-server; can you please file it with them? I'm going to close this issue because we're switching away from webpack-dev-server soon and I'm not sure if webpack will commit resources to this on an old repo.

Thanks for the report, this gives us more reasons to switch libraries!

Collaborator

Timer commented May 24, 2018

I suspect this is a bug with webpack-dev-server; can you please file it with them? I'm going to close this issue because we're switching away from webpack-dev-server soon and I'm not sure if webpack will commit resources to this on an old repo.

Thanks for the report, this gives us more reasons to switch libraries!

@Timer Timer closed this May 24, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment