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

Issue 164302 link

Starred by 4 users

Issue metadata

Status: Verified
Last visit 21 days ago
Closed: Dec 2012
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Bug-Regression

Sign in to add a comment

PDF is not rendered, only black background.

Project Member Reported by, Dec 5 2012

Issue description

Chrome Version       : 25.0.1348.0 (Official Build 170890) dev
Chrome OS Version    : 3342.0.0 (Official Build) dev-channel lumpy

What steps will reproduce the problem?
1.  open a pdf page,
2.  press "Ctrl + P" to open Google Cloud Print
3.  click on  "Cancel" button to close the preview

What is the expected result? What happens instead?
After closing the print preview, the pdf page still remains black color until refreshing the page. 

Please provide any additional information below. Attach a screenshot if
It works fine in Chrome23.0.1271.97

55.2 KB View Download
Labels: Mstone-25
Labels: Action-BisectNeeded
Labels: -Pri-2 -Action-BisectNeeded Pri-1 ReleaseBlock-Stable
I am able to Reproduce this issue on Latest Canary#25.0.1349.2 on Win7.

This is working fine in Latest Dev, Beta & Stable versions.

Good Build#25.0.1338.0
Bad Build#25.0.1342.0

Note: Unable to use the Bisect tool to narrow down the revision range as the Chromium builds are NOT containing the PDF feature on which the current issue is happening.

Status: Started

Comment 6 by, Dec 6 2012

Labels: Noteworthy
Labels: -Feature-PrintPreview Feature-PDF
It's not just print preview.

1. Open new Chrome
2. Navigate
3. Navigate back.
4. Navigate forward.
5. Goto step 3 until screen gets black.

Issue is not inside pdf.dll itself.
Bisecting Chromium with pdf.dll from Chrome 24.0.1312.32 I get to
Labels: Feature-Plugins-Pepper-SDK
Brett, PDF was broken by this patch
Labels: -Noteworthy
There are few more related issues:

1. Debug build every time, when opening pdf as "last opened page" on startup, shows black page.
2. Flickering during windows re-sizing in release build (including current Dev channel). Try to drag bottom right corner of browser when PDF is opened.

Status: Available
Summary: PDF is not rendered, only black background. (was: Pdf page becomes black color after closing the print preview)
It happens after patch 170225, because during some painting (FrameView::paintContents) PluginInstance::bound_graphics_2d_platform_ is NULL.

PluginInstance::bound_graphics_2d_platform_ is NULL because PluginInstance::BindGraphics(_, 0) was called from PluginResource::~PluginResource(). Before patch there was no calls to PluginInstance::BindGraphics(_, 0).

Maybe worth ReleaseBlock-Beta?

Brett, can you take a look?
Status: Assigned
 Issue 165006  has been merged into this issue.
I had the same problem in 25.0.1348.0 dev. Now in Version 25.0.1354.0 dev-m this works correct.
I'm trying to repro in a local build and print preview doesn't work. I have the PDF plugin working, I thought print preview is supposed to go along with the PDF plugin being installed?
This seems to work for me in canary in 1357.
This seems to work for me in canary in 1357.

Comment 18 by, Dec 11 2012

I can't repro original steps, but I see black screen (over PDF) on browser resize.
Canary 1357, Mac Book with retina.
I just hit this on x64 Linux, r171343 from trunk. When I load the attached PDF (by specifying the local filename as a command-line parameter), it reproduces most of the time for me. The real PDF content is briefly rendered before it is clobbered with the black screen of doom.
96.8 KB Download
Still there. Try to resize window dragging bottom right corner when pdf is open.
99 KB View Download
It's maybe timing issue. Debug reproduction is more consistent for me.
Also if you try repro like in #7, even if it's not stay black, there is visible black  flickering.
Just found that disabling both, "Threaded compositing" and "GPU compositing on all pages" also makes reproduction more consistent on Release Canary
Status: Started
Labels: -Feature-Plugins-Pepper-SDK Feature-Plugins-Pepper
Status: Fixed
Project Member

Comment 26 by, Dec 14 2012

The following revision refers to this bug:

r173181 | | 2012-12-14T18:53:24.505406Z

Changed paths:

Only unbind a Graphics2D on destruction when we're actually bound.

Previously if you made a new Graphics2D, bound it, and deleted the previous one, the first one would blindly unbind the current graphics 2D context in its destructor, which leaves you with a blank page.

BUG= 164302 

Review URL:
Labels: TE-Verified-25.0.1363.0canary
Tested this issue on Latest Canary#25.0.1363.0 & Latest Dev#25.0.1363.0 - Working as intended.

Tested Platforms - Win7, Mac OS X 10.8.2 & Linux Precise

Status: Verified
Marking as Verified as per comment #27
Project Member

Comment 29 by, Mar 9 2013

Labels: -Type-Regression -Area-UI -Feature-PDF -Mstone-25 -Feature-Plugins-Pepper Type-Bug-Regression Cr-Content-Plugins-PDF Cr-UI M-25 Cr-Content-Plugins-Pepper
Project Member

Comment 30 by, Apr 5 2013

Labels: Cr-Blink
Project Member

Comment 31 by, Apr 6 2013

Labels: -Cr-Content-Plugins-PDF Cr-Internals-Plugins-PDF
Project Member

Comment 32 by, Apr 6 2013

Labels: Cr-Internals-Plugins
Project Member

Comment 33 by, Apr 6 2013

Labels: -Cr-Content-Plugins-Pepper Cr-Internals-Plugins-Pepper

Sign in to add a comment