-
Notifications
You must be signed in to change notification settings - Fork 155
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
Example page makes my computer explode #82
Comments
On what browser/platform does this happen?
…On Thu 24 Jan, 2019, 12:45 PM Adam Robertson ***@***.*** wrote:
https://klarsys.github.io/angular-material-icons/ gives my
computer/browser CPU creep until it catches fire and ultimately crashes. Is
this something specific to the page, or the library as well? I'm a little
nervous about the long-term effects of running this in my SPAs, but
admittedly haven't had a lot of time to dig into what's doing it. I would
guess it's the animations though, most likely.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#82>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AJ2Dfxza4XvoCTIXX82OYsA29cZI2mCsks5vGV2DgaJpZM4aQRbP>
.
|
Sorry, macOS Mojave, although it happened on High Sierra as well. I leave it open for hours sometimes since it’s a reference document of sorts, and I come back to an untouchably got laptop! |
Can you give us a stacktrace (profile) from the JS engine ? / Are you running it under NoderJS (Electron) or directly in your favourite browser? |
It’s in Chrome, and by “crash”, I mean it takes the whole browser tab down, so there’s no stacktrace. You should be able to reproduce by opening the page and leaving it open for a few hours. |
https://klarsys.github.io/angular-material-icons/ gives my computer/browser CPU creep until it catches fire and ultimately crashes. Is this something specific to the page, or the library as well? I'm a little nervous about the long-term effects of running this in my SPAs, but admittedly haven't had a lot of time to dig into what's doing it. I would guess it's the animations though, most likely.
The text was updated successfully, but these errors were encountered: