Aw, Snap! error often happening after 12.2.0 version upgrade(same works well with 12.1.2)
See original GitHub issueWhich @angular/* package(s) are the source of the bug?
upgrade
Is this a regression?
No
Description
Getting Aw, Snap! error often after the Angular 12.2.0 upgrade!. (same works well with 12.1.4).
Can someone please help me with this?
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in
Angular CLI: 12.2.0
Node: 14.17.0
Yarn: 1.22.5
Anything else?
No response
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Fix "Aw, Snap!" page crashes and other page loading errors
If you're getting the "Aw, Snap" error or another error code instead of a webpage, Chrome is having problems loading. You might also...
Read more >Chrome aw snap, how to solve the error (2022) - SupportHost
In this case Google Chrome opens correctly but shows a Chrome aw snap error, sometimes indicating it is “unable to open this page”....
Read more >How To Fix the “Aw, Snap!” Error in Chrome (8 Methods) - Kinsta
The “Aw, Snap!” message is a generic error in Chrome, and it can have a variety of causes. Use these 8 methods to...
Read more >v12.2.5 Luminous - Ceph Documentation
It contains a range of bug fixes and a few features across Bluestore, CephFS, RBD & RGW. We recommend all the users of...
Read more >v12.2.12 Luminous — Ceph Documentation - Red Hat People
x long term stable release series. We recommend that all users upgrade to this release. Notable Changes¶. In 12.2.11 and earlier releases, keyring...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks, @eneajaho for the response!. I finally found the issue’s root cause. One of my API header payload requests was holding huge data. I just optimized that part and the aw snap error is gone. Thanks for the direction you have suggested!. that helped me!..
Can you try this command:
node --max-http-header-size=100000 ./node_modules/@angular/cli/bin/ng serve
?