Remove --disable-dev-shm-usage from chromedriver settings

Created on 20 March 2024, 3 months ago
Updated 29 March 2024, 3 months ago

Problem/Motivation

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

πŸ“Œ Task
Status

Needs work

Version

11.0 πŸ”₯

Component
OtherΒ  β†’

Last updated less than a minute ago

Created by

πŸ‡¬πŸ‡§United Kingdom alexpott πŸ‡ͺπŸ‡ΊπŸŒ

Live updates comments and jobs are added and updated live.
  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @alexpott
  • Merge request !7108Remove --disable-dev-shm-usage β†’ (Open) created by alexpott
  • Status changed to Needs review 3 months ago
  • πŸ‡¬πŸ‡§United Kingdom alexpott πŸ‡ͺπŸ‡ΊπŸŒ
  • Status changed to RTBC 3 months ago
  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Based on the description of what this does

    Disables using the /dev/shm shared memory file system, which may reduce memory usage during testing.

    This is being removed for performance reasons.

    On that assumption don't see an issue with removal.

  • Status changed to Needs review 3 months ago
  • πŸ‡¬πŸ‡§United Kingdom alexpott πŸ‡ͺπŸ‡ΊπŸŒ

    I thought it was going to make the tests about twice as quick - it did in the past and I can not explain why now.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    @alexpott any recommended way for testing this?

  • πŸ‡¬πŸ‡§United Kingdom longwave UK

    This affects the way Chrome runs inside Docker so as long as all the functional JavaScript tests pass - locally as well as on CI if possible - then I think we are good.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    So should this be RTBC? Or should the tests be ran a few times to make sure nothing random pops up

  • πŸ‡ΊπŸ‡ΈUnited States byrond

    This option has been shown in the past to prevent Chrome from crashing during JavaScript tests. Are you sure there won't be any negative side-effects for removing it?

  • Status changed to Needs work 3 months ago
  • πŸ‡¬πŸ‡§United Kingdom longwave UK

    The IS doesn't explain why we would change this. #5 says there should be a performance increase but that doesn't seem to be the case, if there is no issue to solve should we just leave it alone?

  • πŸ‡¬πŸ‡§United Kingdom alexpott πŸ‡ͺπŸ‡ΊπŸŒ

    In some ways we need to explain why there is not a performance improvement :)

Production build 0.69.0 2024