Skip to content
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

app.getAppMetrics() and ProcessMetric - memory no longer available #16179

Closed
jarrodek opened this issue Dec 22, 2018 · 3 comments
Closed

app.getAppMetrics() and ProcessMetric - memory no longer available #16179

jarrodek opened this issue Dec 22, 2018 · 3 comments

Comments

@jarrodek
Copy link

  • Output of node_modules/.bin/electron --version: v4.0.0
  • Operating System (Platform and Version): Ubuntu 18.04.1 LTS
  • Output of node_modules/.bin/electron --version on last known working Electron version (if applicable): 3.x

Expected Behavior
The ProcessMetric contains memory entry.

Actual behavior
memory information is no longer available.

To Reproduce

let metrics = app.getAppMetrics();
console.log(metrics[0].memory);

Additional Information
I am using app.getAppMetrics() during development to check memory and CPU usage of my app. I have a task manager view as the one available in Chrome. After updated electron to v4 today I noticed that the memory property is no longer available. I saw other issues related to this: #13385, #13414, and #13383 but it's not clear whether you wanted to remove this metric or find the other way to present this information.
Will memory info be available?

@MarshallOfSound
Copy link
Member

@jarrodek That property was deprecated in 3.0 and removed in 4.0. The appropriate runtime warnings were giving in 3.x releases and it was mentioned in our breaking changes document.

This was an intended API removal as a result of a Chromium API change

@jarrodek
Copy link
Author

Are there any plans to introduce new API to get memory info? Just curious. :)

@MarshallOfSound
Copy link
Member

@jarrodek See #13447

Also refs: #14847

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants