Chrome doesn't use swap
0
I have written a single page application that gradually loads objects, and memory usage increases.
At a certain point, Google Chrome shows an error page, and from the log I see
[1:1:1210/224428.169664:FATAL:memory_linux.cc(42)] Out of memory
However, (I'm under linux) from free I see that the RAM is actually filled up, but swap is free. So, why Chrome doesn't continue to work as usual?
linux google-chrome memory swap
edited Dec 10 at 23:49
Christopher Hostage
3,2911028
asked Dec 10 at 22:33
cdarwin
1012
|
show 1 more comment
0
I have written a single page application that gradually loads objects, and memory usage increases.
At a certain point, Google Chrome shows an error page, and from the log I see
[1:1:1210/224428.169664:FATAL:memory_linux.cc(42)] Out of memory
However, (I'm under linux) from free I see that the RAM is actually filled up, but swap is free. So, why Chrome doesn't continue to work as usual?
linux google-chrome memory swap
edited Dec 10 at 23:49
Christopher Hostage
3,2911028
asked Dec 10 at 22:33
cdarwin
1012
1
On modern OSes, RAM is pretty much always filled up. There's always something you can use it for -- disk cache if nothing else. And how much swap is used or free is not really relevant -- what matters is how much swap might be needed. If that exceeds the swap available -- even if no swap is actually used -- then allocations will fail.
– David Schwartz
Dec 10 at 22:45
I think chrome should need another 200 or 400 megabytes, and there are 7 gigabytes of free swap, so I don't understand why it is not used
– cdarwin
Dec 10 at 22:56
1
Is this a 32-bit or 64-bit build of Chrome? It may be out of process address space.
– David Schwartz
Dec 10 at 23:02
I'm using Version 71.0.3578.80 Official Build (64 bit). It seems to me that sometimes chrome crashes even before RAM is filled up
– cdarwin
Dec 10 at 23:36
1
The term "RAM is filled up" is really a meaningless one that you should stop using. Your issue has nothing to do with whether or not RAM is filled up but with whether memory is available for allocation which is almost entirely unrelated. For example, RAM can be empty but no memory available for allocations due to existing unshared, writable file mappings. Or RAM can be completely full of discardable pages and plenty of memory available for allocation. One has almost nothing to do with each other on a modern OS.
– David Schwartz
Dec 10 at 23:48
|
show 1 more comment
0
0
0
I have written a single page application that gradually loads objects, and memory usage increases.
At a certain point, Google Chrome shows an error page, and from the log I see
[1:1:1210/224428.169664:FATAL:memory_linux.cc(42)] Out of memory
However, (I'm under linux) from free I see that the RAM is actually filled up, but swap is free. So, why Chrome doesn't continue to work as usual?
linux google-chrome memory swap
edited Dec 10 at 23:49
Christopher Hostage
3,2911028
asked Dec 10 at 22:33
cdarwin
1012
I have written a single page application that gradually loads objects, and memory usage increases.
At a certain point, Google Chrome shows an error page, and from the log I see
[1:1:1210/224428.169664:FATAL:memory_linux.cc(42)] Out of memory
However, (I'm under linux) from free I see that the RAM is actually filled up, but swap is free. So, why Chrome doesn't continue to work as usual?
linux google-chrome memory swap
linux google-chrome memory swap
edited Dec 10 at 23:49
Christopher Hostage
3,2911028
asked Dec 10 at 22:33
cdarwin
1012
edited Dec 10 at 23:49
Christopher Hostage
3,2911028
asked Dec 10 at 22:33
cdarwin
1012
edited Dec 10 at 23:49
Christopher Hostage
3,2911028
edited Dec 10 at 23:49
Christopher Hostage
3,2911028
edited Dec 10 at 23:49
Christopher Hostage
3,2911028
3,2911028
asked Dec 10 at 22:33
cdarwin
1012
asked Dec 10 at 22:33
cdarwin
1012
asked Dec 10 at 22:33
cdarwin
1012
1012
1
On modern OSes, RAM is pretty much always filled up. There's always something you can use it for -- disk cache if nothing else. And how much swap is used or free is not really relevant -- what matters is how much swap might be needed. If that exceeds the swap available -- even if no swap is actually used -- then allocations will fail.
– David Schwartz
Dec 10 at 22:45
I think chrome should need another 200 or 400 megabytes, and there are 7 gigabytes of free swap, so I don't understand why it is not used
– cdarwin
Dec 10 at 22:56
1
Is this a 32-bit or 64-bit build of Chrome? It may be out of process address space.
– David Schwartz
Dec 10 at 23:02
I'm using Version 71.0.3578.80 Official Build (64 bit). It seems to me that sometimes chrome crashes even before RAM is filled up
– cdarwin
Dec 10 at 23:36
1
The term "RAM is filled up" is really a meaningless one that you should stop using. Your issue has nothing to do with whether or not RAM is filled up but with whether memory is available for allocation which is almost entirely unrelated. For example, RAM can be empty but no memory available for allocations due to existing unshared, writable file mappings. Or RAM can be completely full of discardable pages and plenty of memory available for allocation. One has almost nothing to do with each other on a modern OS.
– David Schwartz
Dec 10 at 23:48
|
show 1 more comment
1
On modern OSes, RAM is pretty much always filled up. There's always something you can use it for -- disk cache if nothing else. And how much swap is used or free is not really relevant -- what matters is how much swap might be needed. If that exceeds the swap available -- even if no swap is actually used -- then allocations will fail.
– David Schwartz
Dec 10 at 22:45
I think chrome should need another 200 or 400 megabytes, and there are 7 gigabytes of free swap, so I don't understand why it is not used
– cdarwin
Dec 10 at 22:56
1
Is this a 32-bit or 64-bit build of Chrome? It may be out of process address space.
– David Schwartz
Dec 10 at 23:02
I'm using Version 71.0.3578.80 Official Build (64 bit). It seems to me that sometimes chrome crashes even before RAM is filled up
– cdarwin
Dec 10 at 23:36
1
The term "RAM is filled up" is really a meaningless one that you should stop using. Your issue has nothing to do with whether or not RAM is filled up but with whether memory is available for allocation which is almost entirely unrelated. For example, RAM can be empty but no memory available for allocations due to existing unshared, writable file mappings. Or RAM can be completely full of discardable pages and plenty of memory available for allocation. One has almost nothing to do with each other on a modern OS.
– David Schwartz
Dec 10 at 23:48
1
1
On modern OSes, RAM is pretty much always filled up. There's always something you can use it for -- disk cache if nothing else. And how much swap is used or free is not really relevant -- what matters is how much swap might be needed. If that exceeds the swap available -- even if no swap is actually used -- then allocations will fail.
– David Schwartz
Dec 10 at 22:45
On modern OSes, RAM is pretty much always filled up. There's always something you can use it for -- disk cache if nothing else. And how much swap is used or free is not really relevant -- what matters is how much swap might be needed. If that exceeds the swap available -- even if no swap is actually used -- then allocations will fail.
– David Schwartz
Dec 10 at 22:45
I think chrome should need another 200 or 400 megabytes, and there are 7 gigabytes of free swap, so I don't understand why it is not used
– cdarwin
Dec 10 at 22:56
I think chrome should need another 200 or 400 megabytes, and there are 7 gigabytes of free swap, so I don't understand why it is not used
– cdarwin
Dec 10 at 22:56
1
1
Is this a 32-bit or 64-bit build of Chrome? It may be out of process address space.
– David Schwartz
Dec 10 at 23:02
Is this a 32-bit or 64-bit build of Chrome? It may be out of process address space.
– David Schwartz
Dec 10 at 23:02
I'm using Version 71.0.3578.80 Official Build (64 bit). It seems to me that sometimes chrome crashes even before RAM is filled up
– cdarwin
Dec 10 at 23:36
I'm using Version 71.0.3578.80 Official Build (64 bit). It seems to me that sometimes chrome crashes even before RAM is filled up
– cdarwin
Dec 10 at 23:36
1
1
The term "RAM is filled up" is really a meaningless one that you should stop using. Your issue has nothing to do with whether or not RAM is filled up but with whether memory is available for allocation which is almost entirely unrelated. For example, RAM can be empty but no memory available for allocations due to existing unshared, writable file mappings. Or RAM can be completely full of discardable pages and plenty of memory available for allocation. One has almost nothing to do with each other on a modern OS.
– David Schwartz
Dec 10 at 23:48
The term "RAM is filled up" is really a meaningless one that you should stop using. Your issue has nothing to do with whether or not RAM is filled up but with whether memory is available for allocation which is almost entirely unrelated. For example, RAM can be empty but no memory available for allocations due to existing unshared, writable file mappings. Or RAM can be completely full of discardable pages and plenty of memory available for allocation. One has almost nothing to do with each other on a modern OS.
– David Schwartz
Dec 10 at 23:48
|
show 1 more comment
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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
});
}
});
draft saved
draft discarded
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%2fsuperuser.com%2fquestions%2f1382461%2fchrome-doesnt-use-swap%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Super User!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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.
draft saved
draft discarded
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%2fsuperuser.com%2fquestions%2f1382461%2fchrome-doesnt-use-swap%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
1
On modern OSes, RAM is pretty much always filled up. There's always something you can use it for -- disk cache if nothing else. And how much swap is used or free is not really relevant -- what matters is how much swap might be needed. If that exceeds the swap available -- even if no swap is actually used -- then allocations will fail.
– David Schwartz
Dec 10 at 22:45
I think chrome should need another 200 or 400 megabytes, and there are 7 gigabytes of free swap, so I don't understand why it is not used
– cdarwin
Dec 10 at 22:56
1
Is this a 32-bit or 64-bit build of Chrome? It may be out of process address space.
– David Schwartz
Dec 10 at 23:02
I'm using Version 71.0.3578.80 Official Build (64 bit). It seems to me that sometimes chrome crashes even before RAM is filled up
– cdarwin
Dec 10 at 23:36
1
The term "RAM is filled up" is really a meaningless one that you should stop using. Your issue has nothing to do with whether or not RAM is filled up but with whether memory is available for allocation which is almost entirely unrelated. For example, RAM can be empty but no memory available for allocations due to existing unshared, writable file mappings. Or RAM can be completely full of discardable pages and plenty of memory available for allocation. One has almost nothing to do with each other on a modern OS.
– David Schwartz
Dec 10 at 23:48