geary on Ubuntu 18.10: large virtual memory consumption reported
up vote
1
down vote
favorite
Ubuntu 18.10 top reports a large consumption of virtual memory by Geary. What is going on here?
17194 stephen 20 0 *99.5g* 814024 88196 S 0.3 10.0 88:12.44 geary
geary
add a comment |
up vote
1
down vote
favorite
Ubuntu 18.10 top reports a large consumption of virtual memory by Geary. What is going on here?
17194 stephen 20 0 *99.5g* 814024 88196 S 0.3 10.0 88:12.44 geary
geary
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Ubuntu 18.10 top reports a large consumption of virtual memory by Geary. What is going on here?
17194 stephen 20 0 *99.5g* 814024 88196 S 0.3 10.0 88:12.44 geary
geary
Ubuntu 18.10 top reports a large consumption of virtual memory by Geary. What is going on here?
17194 stephen 20 0 *99.5g* 814024 88196 S 0.3 10.0 88:12.44 geary
geary
geary
asked Nov 6 at 20:38
Stephen Boston
6992618
6992618
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
It could be memory leaks if Geary has been running for a long time, and so the leaked memory is getting paged to swap. There are a few around, I fix them whenever I can find them, but also compiling Geary against newer versions of vala generally helps.
It is more likely to be the WebKit Gigacage however, which is a security feature that makes it harder for attackers to run malicious code on your computer. It does this by pre-allocating several large (32G) chunks of virtual memory for storing different kinds of web page data separately. Even though it allocates these large chunks, very little of it gets actually used - just enough to display pages.
Since Geary uses WebKitGTK to render email (even plain text email), it will have a number of Gigacages allocated when it starts up. You can confirm this by comparing virtual memory size of other apps that also use WebKitGTK, such as GNOME Web, or by looking at Geary's virtual memory size right after starting it up.
Virtual memory is used for pre-allocations like this, for memory mapping files, and a bunch of other things that don't actually use any memory. So it isn't a very useful metric for determining how much memory a program is using and it's not worth worrying about. Keep an eye on a program's resident set size and the amount of swap being used instead.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
It could be memory leaks if Geary has been running for a long time, and so the leaked memory is getting paged to swap. There are a few around, I fix them whenever I can find them, but also compiling Geary against newer versions of vala generally helps.
It is more likely to be the WebKit Gigacage however, which is a security feature that makes it harder for attackers to run malicious code on your computer. It does this by pre-allocating several large (32G) chunks of virtual memory for storing different kinds of web page data separately. Even though it allocates these large chunks, very little of it gets actually used - just enough to display pages.
Since Geary uses WebKitGTK to render email (even plain text email), it will have a number of Gigacages allocated when it starts up. You can confirm this by comparing virtual memory size of other apps that also use WebKitGTK, such as GNOME Web, or by looking at Geary's virtual memory size right after starting it up.
Virtual memory is used for pre-allocations like this, for memory mapping files, and a bunch of other things that don't actually use any memory. So it isn't a very useful metric for determining how much memory a program is using and it's not worth worrying about. Keep an eye on a program's resident set size and the amount of swap being used instead.
add a comment |
up vote
1
down vote
accepted
It could be memory leaks if Geary has been running for a long time, and so the leaked memory is getting paged to swap. There are a few around, I fix them whenever I can find them, but also compiling Geary against newer versions of vala generally helps.
It is more likely to be the WebKit Gigacage however, which is a security feature that makes it harder for attackers to run malicious code on your computer. It does this by pre-allocating several large (32G) chunks of virtual memory for storing different kinds of web page data separately. Even though it allocates these large chunks, very little of it gets actually used - just enough to display pages.
Since Geary uses WebKitGTK to render email (even plain text email), it will have a number of Gigacages allocated when it starts up. You can confirm this by comparing virtual memory size of other apps that also use WebKitGTK, such as GNOME Web, or by looking at Geary's virtual memory size right after starting it up.
Virtual memory is used for pre-allocations like this, for memory mapping files, and a bunch of other things that don't actually use any memory. So it isn't a very useful metric for determining how much memory a program is using and it's not worth worrying about. Keep an eye on a program's resident set size and the amount of swap being used instead.
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
It could be memory leaks if Geary has been running for a long time, and so the leaked memory is getting paged to swap. There are a few around, I fix them whenever I can find them, but also compiling Geary against newer versions of vala generally helps.
It is more likely to be the WebKit Gigacage however, which is a security feature that makes it harder for attackers to run malicious code on your computer. It does this by pre-allocating several large (32G) chunks of virtual memory for storing different kinds of web page data separately. Even though it allocates these large chunks, very little of it gets actually used - just enough to display pages.
Since Geary uses WebKitGTK to render email (even plain text email), it will have a number of Gigacages allocated when it starts up. You can confirm this by comparing virtual memory size of other apps that also use WebKitGTK, such as GNOME Web, or by looking at Geary's virtual memory size right after starting it up.
Virtual memory is used for pre-allocations like this, for memory mapping files, and a bunch of other things that don't actually use any memory. So it isn't a very useful metric for determining how much memory a program is using and it's not worth worrying about. Keep an eye on a program's resident set size and the amount of swap being used instead.
It could be memory leaks if Geary has been running for a long time, and so the leaked memory is getting paged to swap. There are a few around, I fix them whenever I can find them, but also compiling Geary against newer versions of vala generally helps.
It is more likely to be the WebKit Gigacage however, which is a security feature that makes it harder for attackers to run malicious code on your computer. It does this by pre-allocating several large (32G) chunks of virtual memory for storing different kinds of web page data separately. Even though it allocates these large chunks, very little of it gets actually used - just enough to display pages.
Since Geary uses WebKitGTK to render email (even plain text email), it will have a number of Gigacages allocated when it starts up. You can confirm this by comparing virtual memory size of other apps that also use WebKitGTK, such as GNOME Web, or by looking at Geary's virtual memory size right after starting it up.
Virtual memory is used for pre-allocations like this, for memory mapping files, and a bunch of other things that don't actually use any memory. So it isn't a very useful metric for determining how much memory a program is using and it's not worth worrying about. Keep an eye on a program's resident set size and the amount of swap being used instead.
edited Nov 25 at 22:47
answered Nov 25 at 22:35
Michael Gratton
1115
1115
add a comment |
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.
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.
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%2f1090608%2fgeary-on-ubuntu-18-10-large-virtual-memory-consumption-reported%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