Current time: 07-21-2019, 11:25 PM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
WptAgent docker container is getting bigger
04-09-2019, 11:58 PM (This post was last modified: 04-10-2019 12:14 AM by Daro.)
Post: #1
WptAgent docker container is getting bigger
Hi!
I have private instance of WPT in Docker containers. I have done everything exacly as described here.
Running tests is working fine, but container with agent is getting bigger with every test. At the beginning, its size was about 25MB, but after 25 tests it grown to 650MB. I am running tests from command line using node.js wpt wrapper.
Is that a normal situation, and if not, how can I prevent wptagent container from expanding?

EDIT: here are the parameters I call runTest method with:
{ pollResults: 5, timeout: 600, firstViewOnly: true, video: false, runs: 1 }
Find all posts by this user
Quote this message in a reply
05-01-2019, 03:08 AM
Post: #2
RE: WptAgent docker container is getting bigger
By default, Docker only launches a container with 64MB of shared memory. That might not be enough for headless Chrome on the agent to work based on the size of the page it's checking.

Check to see if there are a bunch of core.<pid> files in the /wptagent folder in the docker container. If there are, you may want to try launching the container with --shm-size=1g to see if that helps keep chrome from dumping whenever it runs out of shared memory.
Find all posts by this user
Quote this message in a reply
05-09-2019, 09:02 PM
Post: #3
RE: WptAgent docker container is getting bigger
Thanks, I think this solved the issue
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)