{"id":17482410,"url":"https://github.com/jack12816/chrome-new-tab-bug","last_synced_at":"2026-04-28T11:34:03.408Z","repository":{"id":152209249,"uuid":"124083162","full_name":"Jack12816/chrome-new-tab-bug","owner":"Jack12816","description":"Crash on PDF files wich are opened on new tabs","archived":false,"fork":false,"pushed_at":"2018-07-25T17:47:09.000Z","size":96,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"master","last_synced_at":"2024-10-19T02:17:28.805Z","etag":null,"topics":["bug","chrome","demo"],"latest_commit_sha":null,"homepage":"https://bugs.chromium.org/p/chromium/issues/detail?id=819220","language":"Ruby","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/Jack12816.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2018-03-06T13:35:55.000Z","updated_at":"2018-07-25T17:47:11.000Z","dependencies_parsed_at":null,"dependency_job_id":"453de96d-2c92-4e56-80e1-c1d5e6c718a9","html_url":"https://github.com/Jack12816/chrome-new-tab-bug","commit_stats":{"total_commits":2,"total_committers":1,"mean_commits":2.0,"dds":0.0,"last_synced_commit":"417be6f63efdad779324c5db8ee3adefd6776807"},"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/Jack12816/chrome-new-tab-bug","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Jack12816%2Fchrome-new-tab-bug","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Jack12816%2Fchrome-new-tab-bug/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Jack12816%2Fchrome-new-tab-bug/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Jack12816%2Fchrome-new-tab-bug/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Jack12816","download_url":"https://codeload.github.com/Jack12816/chrome-new-tab-bug/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Jack12816%2Fchrome-new-tab-bug/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":32379359,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-04-28T11:25:28.583Z","status":"ssl_error","status_checked_at":"2026-04-28T11:25:05.435Z","response_time":56,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.5:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["bug","chrome","demo"],"created_at":"2024-10-18T23:06:00.895Z","updated_at":"2026-04-28T11:34:03.391Z","avatar_url":"https://github.com/Jack12816.png","language":"Ruby","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Chrome new tab bug\n\n- [Whats the issue?](#whats-the-issue)\n- [How to reproduce the issue](#how-to-reproduce-the-issue)\n  - [Requirements](#requirements)\n  - [Expected result](#expected-result)\n  - [Demo video](#demo-video)\n\n## Whats the issue?\n\nLooks like Chrome/Chromium have an issue with the `Page.setDownloadBehavior`\ndevelopment protocol command in combination with the\n`always_open_pdf_externally` preference on new windows/tabs. The Chrome/Chromium\nprocess dies suddenly without any logging. Also, no segmentation fault is\nlogged.\n\n## How to reproduce the issue\n\nYou need to set up the Chrome/Chromium session with the specific preferences and\nthe open a random website. When you click on a link (`target=\"_blank\"` /\n`window.open`) to a PDF file you will see the crash.\n\nI also setup this repository to demonstrate the issue and anybody can try to\nreproduce it. Just take care of the requirements and run the following commands\nto start the example:\n\n```bash\n# Install the required gems\n$ bundle install\n\n# Start the example\n$ bundle exec ruby test.rb\n```\n\n### Requirements\n\n* Linux \u003e= 4.15.0\n* Google Chrome \u003e=64.0.3282.186\n* ChromeDriver \u003e=2.33\n* Ruby \u003e=2.4.0\n* Bundler \u003e= 1.16.0\n\n### Expected result\n\nThe example should keep the Chrome/Chromium process (and window) open for at\nleast 60 seconds. You should also see the PDF file downloaded to the\n`Downloads` directory.\n\n### Demo video\n\n[See the demo video](./demo.webm).\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjack12816%2Fchrome-new-tab-bug","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fjack12816%2Fchrome-new-tab-bug","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fjack12816%2Fchrome-new-tab-bug/lists"}