-
-
Notifications
You must be signed in to change notification settings - Fork 488
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Browser hangs while navigating through report. #38
Comments
I am not able to reproduce this. Can you test out this static report file whether it hangs? I generated it from your attached stats.json file. If this doesn't hang, could you zip over the static HTML report your build created? |
Hi @valscion |
An issue with the platform-specific graphic drivers seems very nasty, and also likely. The library used is a demo variant of some commercial treemap code: https://github.com/th0r/webpack-bundle-analyzer/blob/master/client/vendor/carrotsearch.foamtree.js I don't know the history of that reporter. If we'll get to actually implementing #32 we could create a new reporter with another treemap visualizer easily. Hopefully that wouldn't have issues with your graphics drivers. I don't think there's much we can do to fix your issue, though, sorry 😞 Maybe you could use Edge instead for the visualizer as it seems to work better with your graphics drivers? And also, have you tried updating your drivers, maybe it would help? |
@megaboich |
Issue description
I have quite big report generated for ~4Mb bundle.
While navigating it browser hangs and after time suggests to kill the tab.
This occurs almost immediately in Chrome. In Firefox it lasts a bit longer, but hangs after 3 or 4 navigations. Surprisingly works well in Edge, which shows that this browser could be used at least for something.
Technical info
Debug info
I use it as a plugin to generate static report.
If plugin, what options were provided?
What other Webpack plugins were used?
I thing that is not relevant
Stats.json attached.
stats.zip
Anyway thanks for awesome tool!
The text was updated successfully, but these errors were encountered: