Crash on PDF files wich are opened on new tabs
Reported by
hermann....@gmail.com,
Mar 6 2018
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36 Steps to reproduce the problem: Looks like Chrome/Chromium have an issue with the `Page.setDownloadBehavior` development protocol command in combination with the `always_open_pdf_externally` preference on new windows/tabs. The Chrome/Chromium process dies suddenly without any logging. Also, no segmentation fault is logged. You need to set up the Chrome/Chromium session with the specific preferences and the open a random website. When you click on a link (`target="_blank"` / `window.open`) to a PDF file you will see the crash. What is the expected behavior? The example should keep the Chrome/Chromium process (and window) open for at least 60 seconds. You should also see the PDF file downloaded to the `Downloads` directory. What went wrong? The browser should not suddenly quit. Crashed report ID: How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? N/A Chrome version: 64.0.3282.186 Channel: stable OS Version: 4.15.5 Flash Version: See: https://github.com/Jack12816/chrome-new-tab-bug
,
Mar 6 2018
Nope. I enabled them, then the test took longer to load, but no crash is listed on chrome://crashes.
,
Mar 6 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 6 2018
,
Mar 6 2018
@lukasza, this change isn't part of chrome 64 stable.
,
Mar 6 2018
Maybe try enabling logging and see if anything interesting comes up? https://www.chromium.org/for-testers/enable-logging Also see https://www.chromium.org/for-testers/bug-reporting-guidelines/reporting-crash-bug - If you can get a crash report, that will be helpful.
,
Mar 8 2018
See the logs in the repository. Unfortunately, no crash report was written, even after enabling it. Maybe someone can verify the issue by testing the stuff from the repository I created?
,
Mar 8 2018
I just ran into this issue. There's no crash, just no download happens. It's also applicable for all other (non-PDF) downloads started in a new tab (via both target _blank links and window.open). Page.setDownloadBehavior sets the download behavior, obviously, only for the current page, so the new windows are not affected. Some solution for such situations is needed
,
Mar 8 2018
Thank you for the reproduction :) - so I am not alone with this. But the browser should not quit suddenly when opening download triggering pages on new tabs? From my point of view this a kind of crash, or unexpected behavior.
,
Mar 12 2018
hermann.mayer92@ / outring@ : Could you please us with the sample html testcase to repro the issue from TE-End. Thank You...
,
Mar 14 2018
If this is with Chromium, and you have access to the debuggging symbols for Chromium, try running Chromium inside gdb and see if you catch the crash. e.g. see instructions on https://wiki.ubuntu.com/Chromium/Debugging |
|||
►
Sign in to add a comment |
|||
Comment 1 by dtapu...@chromium.org
, Mar 6 2018Labels: Needs-Feedback