ProfilingPlugin output file crashes Chrome devtools

Bug report

What is the current behavior?

After running ProfilingPlugin and dragging the events.json file into Chrome devtools Performance tab, devtools crashes and closes after “Processing profile…” This seems to happen on larger builds where the JSON file is 116 MiB, but not on smaller builds where it is < 70 MiB.

I’m not sure if this is a bug in Chrome devtools or the webpack plugin (or both) so I figured I’d start here.

If the current behavior is a bug, please provide the steps to reproduce.

  1. Enable ProfilingPlugin on a large build and run webpack. In my scenario, the generated file is 116.6 MiB.
  2. Drag events.json into Chrome devtools Performance tab.
  3. Wait for the file to be loaded and processed.
  4. Devtools closes without showing the results.

What is the expected behavior?

Devtools Performance tab shows flame charts instead of closing.

Other relevant information:
webpack version: 4.15.1
Node.js version: 8.9.1
Operating System: macOS 10.13.5
Additional tools: Chrome 67.0.3396.99 (Official Build) (64-bit)

cc @samccone (let me know if you want my events.json file and I can send you one privately)

Author: Fantashit

2 thoughts on “ProfilingPlugin output file crashes Chrome devtools

  1. I was able to open my profiling output by running Chromium (in my case) with increased memory

    open /Applications/Chromium.app  --args --js-flags="--max_old_space_size=8192"
    

Comments are closed.