Tom Kraak
Tom Kraak
Turns out that the entire test suite runs just fine on Firefox. But I can confirm @justinzelinsky numbers. In latest Chrome it crashes right after 1800 tests have run at...
The memory is definitely growing and eventually crashes at ~900MB. Would a memory leak somewhere in the test suite also explain why Firefox has no issue running the entire suite?
Firefox memory consumption maxes out at 50MB somewhere during the first 1000 tests (mostly application and rendering tests) and then drops just below 10MB for the rest of the suite...
Is it as easy as saying if we had a memory leak it would leak in any browser?
Thanks for the details, much appreciated. I would love to know the answers to your questions :)
@ndekeister-us tanks for your input, much appreciated. I'll most likely start to attack the memory issue by converting to `ember-sinon-qunit`, which is overdue for us anyway.
@monovertex thanks for sharing your findings in such great detail. It's very impressive and much appreciated. This seems to confirm our earlier inclination that this is a bug in Chrome...
Thanks for reporting this issue. Is `--with-modules` still valid? It's not included in the list of options that I see when I run `brew info emacs-mac`.
Thank you. I did rebuild an M1 `--with-native-compilation` and haven't seen any problems. I was going to do the same with my M2, but now I'm hesitant because of the...
@variemai what exact Apple hardware are you on?