New issue
Advanced search Search tips

Issue 692905 link

Starred by 4 users

Issue metadata

Status: Duplicate
Merged: issue 334474
Owner:
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Chrome get stuck in a loop opening tabs when opening downloaded file.

Project Member Reported by holte@chromium.org, Feb 16 2017

Issue description

Chrome Version: 56.0.2924.87
OS: Win 10

What steps will reproduce the problem?
(1) Go to http://www.revenue.state.mn.us/individuals/individ_income/Pages/Individual_Income_Tax_Forms.aspx
(2) Click the link to download "2016 Minnesota Individual Income Tax Instructions"
(3) Wait for the file to download

What is the expected result?
The file is downloaded, and maybe opens to a pdf viewer.

What happens instead?
When the file is download, chrome attempts to open it in a new tab.  Instead of showing it in a new tab, the tab starts a download of the same file with " (1)" appended to the filename and closes immediately.  The new file download completes instantly and opens in another new tab, which starts another download with another " (1)" attached, and the process keeps repeating with increasingly long filenames.

To stop the process, close the chrome window, and maybe delete a bunch of files from the downloads directory.
 
Labels: -Pri-3 M-58 OS-Windows Pri-2
Owner: xingliu@chromium.org
Status: Assigned (was: Untriaged)
Doesn't repro on chromebook.  xingliu@ can you try to repro and grab some logs?
Didn't repo on win 7. Will try to find a win 10 to debug.
Labels: Needs-Feedback
Can't reproduce on  56.0.2924.87 win 10 home, please provide some more details:

Which pdf viewer do you use, there is a setting "Chrome PDF Viewer" in chrome://plugins, is it enabled? or use external pdf viewer.

It'also helpful to get logs following this : https://support.google.com/chrome/a/answer/6271282?hl=en
and try to repro the bug and attach the chrome_debug.log file.

Another helpful feedback would be attach the history database file, location:
C:\Users\[win username]\AppData\Local\Google\Chrome\User Data\Default\History
Labels: -M-58 M-59
Punting from M58.  Still waiting on feedback and we already branched.

Comment 5 by holte@chromium.org, Mar 13 2017

Checking chrome://plugins, I see:

Chrome PDF Viewer (2 files) (Disabled by enterprise policy)

So I'm guessing what is happening is that I had Chrome set up as the default pdf viewer, then it got disabled by policy. Now when it opens the file it tries to download the file from local disk, and then open it in Chrome and loops.  This makes sense, but is probably not the best failure mode.

Comment 6 by centaur@google.com, Mar 14 2017

I am experiencing very similar behavior on a Mac. I do not have Chrome set up as my default PDF viewer as I use Adobe Acrobat. I have further disabled the PDF viewer in Chrome. Roughly once per day or every other day, however, Chrome resets itself to be the default PDF viewer application, and then the download loop manifests itself. Very occasionally it can be stopped by opening Info on a PDF file, changing the application that opens the file, and then changing all. Normally, however, you have to kill Chrome (and delete all the extra copies).

Comment 7 by centaur@google.com, Mar 31 2017

Update: this happens sometimes when I'm actually trying to download the file, not view it. So Chrome is making two errors: trying to open links that should be download links, and setting itself as the default application when it should not be.
Thanks for all the feedback, starting to look at this.

I can produce a very similar scenario in win laptop that if I download a pdf, and enable settings> show advanced settings > content settings > pdf document > Open PDF files in the default PDF viewer application.

Then click on the downloaded file at the bottom, it will download it again and attach another "(1)" to the file name.

Basically attach another "(1)" is done in download code, where chrome should just open the file instead of route it to download system.

Comment 9 by centaur@google.com, Mar 31 2017

Woot! Glad you were able to repro. Good luck fixing it. One more bit of polish for Chrome!
Mergedinto: 334474
Status: Duplicate (was: Assigned)

Sign in to add a comment