Chromium on mac use disk space

[Paxa]

I downloaded latest Chromium and it works well but I noticed that one folder become 30GB which contain just copies of chromium

du -cksh /var/folders/n9/b__lxh7j1_xcwg4k_8j2_39m0000gp/X/org.chromium.Chromium.code_sign_clone
 30G   /var/folders/n9/b__lxh7j1_xcwg4k_8j2_39m0000gp/X/org.chromium.Chromium.code_sign_clone
 30G    total


ls /var/folders/n9/b__lxh7j1_xcwg4k_8j2_39m0000gp/X/org.chromium.Chromium.code_sign_clone/*
/var/folders/n9/b__lxh7j1_xcwg4k_8j2_39m0000gp/X/org.chromium.Chromium.code_sign_clone/code_sign_clone.0IYb9c:
Chromium.app

/var/folders/n9/b__lxh7j1_xcwg4k_8j2_39m0000gp/X/org.chromium.Chromium.code_sign_clone/code_sign_clone.1Lwcla:
Chromium.app

/var/folders/n9/b__lxh7j1_xcwg4k_8j2_39m0000gp/X/org.chromium.Chromium.code_sign_clone/code_sign_clone.1izaQN:
Chromium.app

And after every execution of test there is new copy added

Command and arguments that ferrum run:

/Applications/Chromium.app/Contents/MacOS/Chromium
 --headless
 --hide-scrollbars
 --mute-audio
 --enable-automation
 --disable-web-security
 --disable-session-crashed-bubble
 --disable-breakpad
 --disable-sync
 --no-first-run
 --use-mock-keychain
 --keep-alive-for-test
 --disable-popup-blocking
 --disable-extensions
 --disable-component-extensions-with-background-pages
 --disable-hang-monitor
 --disable-features=site-per-process,IsolateOrigins,TranslateUI
 --disable-translate
 --disable-background-networking
 --enable-features=NetworkService,NetworkServiceInProcess
 --disable-background-timer-throttling
 --disable-backgrounding-occluded-windows
 --disable-client-side-phishing-detection
 --disable-default-apps
 --disable-dev-shm-usage
 --disable-ipc-flooding-protection
 --disable-prompt-on-repost
 --disable-renderer-backgrounding
 --disable-site-isolation-trials
 --force-color-profile=srgb
 --metrics-recording-only
 --safebrowsing-disable-auto-update
 --password-store=basic
 --no-startup-window
 --remote-allow-origins=*
 --use-angle=metal
 --remote-debugging-port=0
 --remote-debugging-address=127.0.0.1
 --window-size=1200,800
 --user-data-dir=/var/folders/n9/b__lxh7j1_xcwg4k_8j2_39m0000gp/T/ferrum_user_data_dir_20241118-61577-1g1o7tx
 --remote-allow-origins=*

[route]

That's a question to Chrome, why they create it on every context creation and why they don't clean up polluted space.
https://cocalc.com/github/chromium/chromium/blob/main/chrome/browser/mac/code_sign_clone_manager.h
Everything that Ferrum creates, it cleans up (ferrum_user_data_dir).

[dvkch]

You can disable this behaviour for now using the following code, inspired from teamcapybara/capybara#2795 (comment)

Capybara.register_driver(:cuprite) do |app|
  Capybara::Cuprite::Driver.new(
    app, window_size: [1200, 800], timeout: 60, process_timeout: 15, js_errors: true, headless: true,
    # prevents the creation of /private/var/folders/zx/*/X/com.google.Chrome.code_sign_clone
    browser_options: { 'disable-features': 'MacAppCodeSignClone' }
  )
end

[route]

Pretty decent find! Thank you I think we should turn it on by default! @dvkch mind creating a PR?