-
Notifications
You must be signed in to change notification settings - Fork 287
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
Chrome freezes tab with Ember Inspector extension #690
Comments
Seems it also freezes if extension is just enabled, but you're not in |
I have no idea if it's linked, but I have another case of Chrome + Firefox freezing + using 100% of CPU when selecting a specific model on the Data panel... Details and a minimum reproduction setup are here (well, as minimum as I could make that). See the readme for all the details. |
For what it's worth, it seems other people have been posting messages on Slack related to problems that look similar : https://embercommunity.slack.com/archives/C04ENQPFW/p1501207850719655
|
For me the problem is not visible with ember-data 2.13.2 and is there with 2.14.x, whatever the x (up until 7). |
Same here, happens only when the data tab of the ember inspector is open. In my case it's caused by
100% of the CPU is used, the memory keeps increasing and nothing is showed in the console
Initially thought something was wrong in my code and took me a long time to figure it wasn't the case, as I always keep the data tab open! 😅 |
@stephanebruckert Everything is same for me. Even the last sentence 😄 It's just impossible to work with Ember Inspector, but I really need it to see the routes, data and so on. |
Also happening to me, luckily it did not take me long to figure out it wasn't my fault considering it is a new project 😄 |
I wrote my
according to emberjs/data#4972 (comment) |
Check that your data is loading fine, had an issue with it in the last month, and it was caused by malformed/corrupt data, that freezes data tab. I had to comment the queries until I found the model that was causing the problem. YMMV |
No kind of malformed data should silently bug and crash your tab, without even a single error message... |
I agree, but that probably will unlock other people with the same problem while is fixed :) |
If this helps anyone, here's a project and steps to repro the issue: https://github.com/sammynave/freeze |
Got hit by this today, on [email protected] seems to happen when I delete an unsaved record |
experiencing the same issue.... |
I use Chrome (Version 60.0.3112.90 (Official Build) (64-bit)) + the latest Ember Inspector extension. |
have the same problem, any news? :( |
Thank you all for the detailed bug report. I was able to reproduce it and I'm investigating the issue. |
… count actually changed Fixes emberjs/ember-inspector#690 The issue: In some cases, Ember Data's `peekAll` triggers `arrayContentDidChange` on the record array manager's live record array even if the records didn't change. One example case is when we call `unloadRecord` and then `peekAll` within the same run loop. The `peekAll` will trigger the array observer's `didChange` callback (with zero changes). This is generally harmless as long as we guard against that in our data adapter. Without the guard, we risk causing an infinite recursion because our `didChange` observer itself calls `peekAll`, which in the above scenario will re-trigger the observer and so on.
I identified the issue and proposed a solution emberjs/ember.js#15604. |
… count actually changed Fixes emberjs/ember-inspector#690 The issue: In some cases, Ember Data's `peekAll` triggers `arrayContentDidChange` on the record array manager's live record array even if the records didn't change. One example case is when we call `unloadRecord` and then `peekAll` within the same run loop. The `peekAll` will trigger the array observer's `didChange` callback (with zero changes). This is generally harmless as long as we guard against that in our data adapter. Without the guard, we risk causing an infinite recursion because our `didChange` observer itself calls `peekAll`, which in the above scenario will re-trigger the observer and so on. (cherry picked from commit 7bd47da)
… count actually changed Fixes emberjs/ember-inspector#690 The issue: In some cases, Ember Data's `peekAll` triggers `arrayContentDidChange` on the record array manager's live record array even if the records didn't change. One example case is when we call `unloadRecord` and then `peekAll` within the same run loop. The `peekAll` will trigger the array observer's `didChange` callback (with zero changes). This is generally harmless as long as we guard against that in our data adapter. Without the guard, we risk causing an infinite recursion because our `didChange` observer itself calls `peekAll`, which in the above scenario will re-trigger the observer and so on. (cherry picked from commit 7bd47da)
Hello,
I'm using latest Chrome and Ember Inspector extension. The problem is, when you enable Ember Inspector extension and you go to the
Data
and useunloadRecord()
for e.g. I haveDelete
button which unloads record after delete and when I press it Chrome tab will freeze and uses a lot of memory and CPU. When I turn off ember extension everything works fine with developer tools opened, but with ember inspector extension I get this. Nothing helped, I even cleaned cache, settings and so on.If you don't open Developer Tools with Ember - everything is OK.
If you open Developer Tools for e.g. with Console tab - everything is OK.
If you open Developer Tools with Ember - everything is OK.
If you open Developer Tools with Ember and you go the
Data
- chrome tab freezes and uses a lot of resources.The text was updated successfully, but these errors were encountered: