New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 592263 link

Starred by 12 users

Issue metadata

Status: Duplicate
Merged: issue 594343
Owner:
Closed: Mar 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

PDF flickers during rendering

Reported by sits...@gmail.com, Mar 6 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36

Steps to reproduce the problem:
1. In Chrome go to http://delivery.acm.org/10.1145/2800000/2795228/p70-tanenbaum.pdf?ip=91.125.76.79&id=2795228&acc=OA&key=4D4702B0C3E38B35%2E4D4702B0C3E38B35%2E4D4702B0C3E38B35%2E86A1BAB8B1D3D34C&CFID=589212149&CFTOKEN=59916877&__acm__=1457295412_ecde93229aae2f6e9376cfac4e61a56b .
2. Start scrolling.

What is the expected behavior?
PDF pages to be displayed.

What went wrong?
While scrolling the proper page is displayed before a grey background is drawn over top. Sometimes little pieces of the page are visible through the grey.

Did this work before? N/A 

Chrome version: 49.0.2623.75  Channel: n/a
OS Version: OS X 10.9.5
Flash Version: Shockwave Flash 20.0 r0

PDF opens correctly in OS X Preview.
 
PDF glitch.png
87.4 KB View Download

Comment 1 by sits...@gmail.com, Mar 6 2016

(Wanted to assign this to component:Internals>Plugins>PDF but seemingly I was never given the option to select it)
Components: Internals>Plugins>PDF
Labels: Needs-Feedback
Tested the issue on Mac 10.10.5, Windows 7, Ubuntu 14.04 using 49.0.2623.75 with below steps:

1.Opened URL: http://delivery.acm.org/10.1145/2800000/2795228/p70-tanenbaum.pdf?ip=91.125.76.79&id=2795228&acc=OA&key=4D4702B0C3E38B35%2E4D4702B0C3E38B35%2E4D4702B0C3E38B35%2E86A1BAB8B1D3D34C&CFID=589212149&CFTOKEN=59916877&__acm__=1457295412_ecde93229aae2f6e9376cfac4e61a56b in chrome and firefox.
2.Got error 'An error occurred while processing your request.
Reference #50.cf100217.1457329086.5a6b160'.
3.Observed the same behavior in firefox also.

Please find attached screenshot.

sitsofe@Could you please provide another sample URL where we can test this issue for further triage.
592263.png
74.2 KB View Download
Same here:

OSX 10.9.5
version 49.0.2623.75 (64-bit)

Using all those pdf files
http://www.tcpdf.org/examples.php
We are seeing this issue in our organization as well. It appears to have started last week. I've just seen it live today.

I simply used the US governments 1040EZ tax form.

https://www.irs.gov/pub/irs-pdf/i1040ez.pdf

I have attached a video of the issue as it is occurring. I was also made aware earlier this morning that a print preview of a pdf appeared "completely blank" for one user and a screenshot of that is also attached.

I also disabled several of the user's extensions (including evernote) that I thought may be confusing the issue.
pdf_chrome_flash.mov
14.2 MB Download
pdf.png
124 KB View Download
print.png
90.0 KB View Download

Comment 6 by sits...@gmail.com, Mar 9 2016

Could someone put the word "gray" into the title of this issue and remove Needs-Feedback?

Comment 7 by sits...@gmail.com, Mar 9 2016

This issue isn't present on another OS X 10.9.5 machine with Chrome 48.0.2564.116 (Official Build) (64-bit).

Comment 8 by etco...@gmail.com, Mar 9 2016

Various reports of this in the Chrome help forum: https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/chrome/UyfmhFzQj4c/CfeqfZfaCgAJ

It does appear to have started with Version 49.0.2623.75 (64-bit) on MAC for several folks.
Project Member

Comment 9 by sheriffbot@chromium.org, Mar 9 2016

Labels: -Needs-Feedback Needs-Review
Owner: ssamanoori@chromium.org
Status: Assigned (was: Unconfirmed)
Thank you for providing more feedback. Assigning to requester "ssamanoori@chromium.org" for another review.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot
Adding that this issue still occurs on 10.9.5 / 13F1603 with Chrome 49.0.2623.87.

Have not verified with other versions of OS X yet.

Comment 11 by sits...@gmail.com, Mar 9 2016

In the link provided by etcohen there is a common theme of users seeing the problem being on OS X 10.9.5 coupled with Chrome 49. In that link one user also says upgrading to OS X 10.11 resolved the problem.
We are seeing the same problem.  OS X 10.9.5 with Chrome 49

Comment 13 by etco...@gmail.com, Mar 14 2016

Various folks in the productforums thread (link above), starting with user12347, are reporting success with a work-around:
    I have this issue as well (mac os 10.9.5, chrome  49.0.2623.87 (64-bit))

    Unchecking Preferences > System > "use hardware acceleration when available" seems to have fixed it, so hopefully hardware acceleration is generally not available on my system :-)

I can confirm that the unchecking of "use hardware acceleration when available" fixes the issue (on two macs ... we have another 3-5 users with this issue).
Cc: tapted@chromium.org shrike@chromium.org
Owner: ----
Status: Untriaged (was: Assigned)
+current / next mac bug triager
Cc: -shrike@chromium.org
Unable to reproduce on MacBook Pro with Chrome 49.0.2623.87, with hardware acceleration option checked. Does the issue occur in the latest Canary?

Comment 17 by lilha...@gmail.com, Mar 20 2016

Yes, this issue still exists in the latest dev and Canary.
(with hardware acceleration checked)
Tried both
51.0.2679.0 dev
51.0.2685.0 Canary

OS X 10.9.5

 Issue 595963  has reported the same problem(merge suggestion)



ps: I thought an issue I reported recently  Issue 596010  is related but it turned it was not quite since with hardware acceleration unchecked, it was still there.
I'm able to reproduce the issue on a MacBook Air (13", mid 2012) running OSX 10.9.5 with the latest Canary (51.0.2685.0 canary, 64-bit).
 Issue 595963  has been merged into this issue.
Cc: -tapted@chromium.org raymes@chromium.org
Labels: -Type-Bug -Needs-Review Type-Bug-Regression
Owner: ccameron@chromium.org
Status: Assigned (was: Untriaged)
Could someone who is seeing this go to chrome://gpu, and attach what you see there?

I wasn't able to reproduce on 10.9.5 (13F1134), with
 - https://www.irs.gov/pub/irs-pdf/i1040ez.pdf
 - MacPro5,1 (Radeon HD 5770), non-retina screen
 - scrolling with each of: {bluetooth trackpad, mouse wheel, scroll thumb drag}

Tested:
 - 48.0.2564.116 [before regression]
 - 49.0.2623.87
 - 51.0.2685.0

There's probably something here - maybe something similar to  Issue 543324 . Not sure why this would be specific to PDF though. Also seems to be specific to 10.9 (so if it's an option - taking the free upgrade from Apple to 10.11 would give you the best fix).

ccameron@ probably knows what to do (maybe we need something like r358579?
I'm affected and here ist my chrome://gpu output.
chrome---gpu.pdf
653 KB Download
Mergedinto: 594343
Status: Duplicate (was: Assigned)
Definitely  issue 594343 .
Here is another gpu output. Disabling hardware-acceleration has been our workaround for 10.9.5 clients for now.
chrome---gpu.pdf
139 KB Download

Comment 24 by m1g...@gmail.com, Mar 24 2016

Another Mac Book Air gpu output file. I am using Kami extension PDF viewer as a workaround. 
chrome___gpu.pdf
139 KB Download
I re-enabled hardware acceleration and it is still present.  
Version 49.0.2623.87 (64-bit)
Things I have noticed.
Machines with heavy processing power are not as deeply affected by this. I have encountered about 10 users including myself that had this happen. ON my machine, I was still able to print and kind of view the files if I scrolled.  a user with half the ram of my machine can not do anything. I also see that this is not an immediate issue. As in something triggers this to happen, then it is there until acceleration is disabled.
thanks for the workaround for now though it is much appreciated 
chrome___gpu.pdf
137 KB Download
version 49.0.2623.108 (64-bit) the issue is not present
Version 49.0.2623.110 (64-bit)
Mac OS X Version 10.9.5

Still an issue; turning off hardware acceleration continues to provide a temporary fix.

Sign in to add a comment