Electron `chrome --type=renderer --field-trial-handle=…` won't shut down, eats up Memory
I am trying to build an app with electron. When I do this, however, it appears that several chrome processes are created that don't shut down after closing electron. These processes eat up a lot of memory that slow down my computer. Most of the processes are called something like chrome --type=renderer --field-trial-handle=...
.
They occur even when I try to run the electron quick start app. I cannot figure out a way to stop these processes besides restarting the computer.
Here is a screenshot of these processes from my system monitor:
This is what happens when I try to end the process. Some sort of weird non-functioning dialogue box pops up:
Questions.
- Is this problem in fact created by electron?
- Is there a way to shut these down within electron (e.g. via a flag)?
- Is there a way to shut these processes down without restarting?
- Would it just be better to submit an issue to the electron repo?
Info.
- OS: Ubuntu 16.04 LTS
- Electron Version: v1.7.9
- Chrome Version: Version 61.0.3163.100 (Official Build) (64-bit)
google-chrome memory-usage system-monitor electron
add a comment |
I am trying to build an app with electron. When I do this, however, it appears that several chrome processes are created that don't shut down after closing electron. These processes eat up a lot of memory that slow down my computer. Most of the processes are called something like chrome --type=renderer --field-trial-handle=...
.
They occur even when I try to run the electron quick start app. I cannot figure out a way to stop these processes besides restarting the computer.
Here is a screenshot of these processes from my system monitor:
This is what happens when I try to end the process. Some sort of weird non-functioning dialogue box pops up:
Questions.
- Is this problem in fact created by electron?
- Is there a way to shut these down within electron (e.g. via a flag)?
- Is there a way to shut these processes down without restarting?
- Would it just be better to submit an issue to the electron repo?
Info.
- OS: Ubuntu 16.04 LTS
- Electron Version: v1.7.9
- Chrome Version: Version 61.0.3163.100 (Official Build) (64-bit)
google-chrome memory-usage system-monitor electron
add a comment |
I am trying to build an app with electron. When I do this, however, it appears that several chrome processes are created that don't shut down after closing electron. These processes eat up a lot of memory that slow down my computer. Most of the processes are called something like chrome --type=renderer --field-trial-handle=...
.
They occur even when I try to run the electron quick start app. I cannot figure out a way to stop these processes besides restarting the computer.
Here is a screenshot of these processes from my system monitor:
This is what happens when I try to end the process. Some sort of weird non-functioning dialogue box pops up:
Questions.
- Is this problem in fact created by electron?
- Is there a way to shut these down within electron (e.g. via a flag)?
- Is there a way to shut these processes down without restarting?
- Would it just be better to submit an issue to the electron repo?
Info.
- OS: Ubuntu 16.04 LTS
- Electron Version: v1.7.9
- Chrome Version: Version 61.0.3163.100 (Official Build) (64-bit)
google-chrome memory-usage system-monitor electron
I am trying to build an app with electron. When I do this, however, it appears that several chrome processes are created that don't shut down after closing electron. These processes eat up a lot of memory that slow down my computer. Most of the processes are called something like chrome --type=renderer --field-trial-handle=...
.
They occur even when I try to run the electron quick start app. I cannot figure out a way to stop these processes besides restarting the computer.
Here is a screenshot of these processes from my system monitor:
This is what happens when I try to end the process. Some sort of weird non-functioning dialogue box pops up:
Questions.
- Is this problem in fact created by electron?
- Is there a way to shut these down within electron (e.g. via a flag)?
- Is there a way to shut these processes down without restarting?
- Would it just be better to submit an issue to the electron repo?
Info.
- OS: Ubuntu 16.04 LTS
- Electron Version: v1.7.9
- Chrome Version: Version 61.0.3163.100 (Official Build) (64-bit)
google-chrome memory-usage system-monitor electron
google-chrome memory-usage system-monitor electron
asked Nov 12 '17 at 18:05
webelowebelo
1064
1064
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
It is not caused by Electron.
I was searching for what they were doing consuming my memory when I ran across your question. But I am not using or even have Electron installed. I instead run Brave browser which is built upon chromium.
So this must be some chrome shit. I am new to this too.
It is not clear to me that brave does not use electron (though I have not looked into it closely). Check out the search for "electron" in their github here. However, this may well be a Chromium issue, since both certainly do use Chromium.
– webelo
yesterday
Also, @bign dhakal just a quick note about answers: usually your note would be added as a comment to the question, not as an answer, because it does not solve the issue but does potentially help out with a solution. Your reputation might be too low to comment, though, so maybe that's why you did it?
– webelo
yesterday
i dont know much about askubuntu and its reputation...i just saw your post and said what i knew :)
– bigndhakal
5 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f975767%2felectron-chrome-type-renderer-field-trial-handle-wont-shut-down-eats%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It is not caused by Electron.
I was searching for what they were doing consuming my memory when I ran across your question. But I am not using or even have Electron installed. I instead run Brave browser which is built upon chromium.
So this must be some chrome shit. I am new to this too.
It is not clear to me that brave does not use electron (though I have not looked into it closely). Check out the search for "electron" in their github here. However, this may well be a Chromium issue, since both certainly do use Chromium.
– webelo
yesterday
Also, @bign dhakal just a quick note about answers: usually your note would be added as a comment to the question, not as an answer, because it does not solve the issue but does potentially help out with a solution. Your reputation might be too low to comment, though, so maybe that's why you did it?
– webelo
yesterday
i dont know much about askubuntu and its reputation...i just saw your post and said what i knew :)
– bigndhakal
5 hours ago
add a comment |
It is not caused by Electron.
I was searching for what they were doing consuming my memory when I ran across your question. But I am not using or even have Electron installed. I instead run Brave browser which is built upon chromium.
So this must be some chrome shit. I am new to this too.
It is not clear to me that brave does not use electron (though I have not looked into it closely). Check out the search for "electron" in their github here. However, this may well be a Chromium issue, since both certainly do use Chromium.
– webelo
yesterday
Also, @bign dhakal just a quick note about answers: usually your note would be added as a comment to the question, not as an answer, because it does not solve the issue but does potentially help out with a solution. Your reputation might be too low to comment, though, so maybe that's why you did it?
– webelo
yesterday
i dont know much about askubuntu and its reputation...i just saw your post and said what i knew :)
– bigndhakal
5 hours ago
add a comment |
It is not caused by Electron.
I was searching for what they were doing consuming my memory when I ran across your question. But I am not using or even have Electron installed. I instead run Brave browser which is built upon chromium.
So this must be some chrome shit. I am new to this too.
It is not caused by Electron.
I was searching for what they were doing consuming my memory when I ran across your question. But I am not using or even have Electron installed. I instead run Brave browser which is built upon chromium.
So this must be some chrome shit. I am new to this too.
answered 2 days ago
bigndhakalbigndhakal
62
62
It is not clear to me that brave does not use electron (though I have not looked into it closely). Check out the search for "electron" in their github here. However, this may well be a Chromium issue, since both certainly do use Chromium.
– webelo
yesterday
Also, @bign dhakal just a quick note about answers: usually your note would be added as a comment to the question, not as an answer, because it does not solve the issue but does potentially help out with a solution. Your reputation might be too low to comment, though, so maybe that's why you did it?
– webelo
yesterday
i dont know much about askubuntu and its reputation...i just saw your post and said what i knew :)
– bigndhakal
5 hours ago
add a comment |
It is not clear to me that brave does not use electron (though I have not looked into it closely). Check out the search for "electron" in their github here. However, this may well be a Chromium issue, since both certainly do use Chromium.
– webelo
yesterday
Also, @bign dhakal just a quick note about answers: usually your note would be added as a comment to the question, not as an answer, because it does not solve the issue but does potentially help out with a solution. Your reputation might be too low to comment, though, so maybe that's why you did it?
– webelo
yesterday
i dont know much about askubuntu and its reputation...i just saw your post and said what i knew :)
– bigndhakal
5 hours ago
It is not clear to me that brave does not use electron (though I have not looked into it closely). Check out the search for "electron" in their github here. However, this may well be a Chromium issue, since both certainly do use Chromium.
– webelo
yesterday
It is not clear to me that brave does not use electron (though I have not looked into it closely). Check out the search for "electron" in their github here. However, this may well be a Chromium issue, since both certainly do use Chromium.
– webelo
yesterday
Also, @bign dhakal just a quick note about answers: usually your note would be added as a comment to the question, not as an answer, because it does not solve the issue but does potentially help out with a solution. Your reputation might be too low to comment, though, so maybe that's why you did it?
– webelo
yesterday
Also, @bign dhakal just a quick note about answers: usually your note would be added as a comment to the question, not as an answer, because it does not solve the issue but does potentially help out with a solution. Your reputation might be too low to comment, though, so maybe that's why you did it?
– webelo
yesterday
i dont know much about askubuntu and its reputation...i just saw your post and said what i knew :)
– bigndhakal
5 hours ago
i dont know much about askubuntu and its reputation...i just saw your post and said what i knew :)
– bigndhakal
5 hours ago
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f975767%2felectron-chrome-type-renderer-field-trial-handle-wont-shut-down-eats%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown