My MBP is 10.13.6. And Canary 70.0.3530 works fine, but 70.0.3532 can reproduce this issue though. Also I notice in your recording, the bad version is 70.0.3531. So most probably the problem is introduced in between 3530 and 3531. Please double confirm!

I tried to do a bisect with chromium, but there is no 'Report issue' option in chromium...

As a matter of fact, the change in my cl,  https://chromium.googlesource.com/chromium/src/+/09cd5826e743af9dbcbde8ab36f73f5e0bd55f6c, has been enabled to all channels by Finch. And I cannot reproduce it with Stable too. 

Gave a quick glance to the changes between 70.3531 and 70.3532, https://chromium.googlesource.com/chromium/src/+log/a5a30e72b73764a8ccc70e551e312fc972fe2e79..67552a19956c647476f79ab12af45dc91762c3a5, and can't tell the offending cl easily.

We need to find the owner of 'Report an issue' and find a way to enable it in chromium for a test.

Over to OWNER of the code in question.

https://cs.chromium.org/chromium/src/chrome/browser/ui/webui/settings/md_settings_localized_strings_provider.cc?q=page_report_an_issue&sq=package:chromium&dr=C&l=317

Let's try a finer grained by bisect.

At first glance, IOSurfaceCapturer sounds extremely related to the symptoms.

I would ask: Can you reproduce the issue my forcing the feature on with --enable-features? What about turning it off via --disable-features flag?

Yes, disable IOSurfaceCapturer can make the problem disappear in latest Canary.
But meantime, enable IOSurfaceCapturer will not cause any problem in earlier Canary versions. See the attachments of screenshots with Canary 75.3531 and 75.3532. You can see that the problem starts since 75.3532.
And IOSurfaceCapturer has been enabled 100% everywhere, you can't see this problem on Stable too. Also the normal screencapture, i.e. go/Presentation, works fine too in latest Canary.

I guess this is a render issue in Report An Issue, as IOSurfaceCapturer has twice the performance, e.g. higher framerate now.

Deleted: Screen Shot 2018-08-31 at 11.14.32 AM.png 312 KB

	Screen Shot 2018-08-31 at 11.14.32 AM.png 312 KB View Download

Missed the screenshot with 70.3531. Attached it here.

Deleted: Screen Shot 2018-08-31 at 11.13.08 AM.png 328 KB

	Screen Shot 2018-08-31 at 11.13.08 AM.png 328 KB View Download

adding label 'ET-MUM-Reported' as we need that label to track bugs.

As per comment #5&6 removing Needs-Bisect label.Please add if its required.

Thank You!

Hi, some users of my Chrome extension have reported a similar issue with the chrome.tabs.captureVisibleTab creating all black images. They are *all* on v69.

I also experienced this just after updating from Chrome 68 -> Chrome 69 along with some system updates (on Mac OS 10.13.6). After 2 hours of an utterly confounding debugging experience, I restarted my computer and the problem was resolved.

I currently have one user on Windows 10.0.0 and Chrome 69.0.3497.100 who is still getting this issue after restart. They even recreated it on this very simple extension: https://github.com/mrcoles/test-chrome-extension-capturetab

I have attached their chrome://versions content to this comment.

Deleted: versions-user-with-black-screenshots.txt 1.9 KB

versions-user-with-black-screenshots.txt 1.9 KB View Download

Hi peter, your issue totally has nothing to do with this one, which is about IOSurface capture to capture the screen on MaxOSX. Your problem is on windows and tabs.captureVidibleTab() will not invoke desktopCapture at all. So please file another issue.

Okay. It sounds like the problem may already be fixed?

If so, feel free to close the issue.

I'm assigning the issue to braveyao@ as it is most related to those changes.

It seems that it works again in M71, tested with Canary 71.3578. No idea what change fixed this. Definitely I didn't do any thing recently.

Be aware that M70 may still not work. It's better to find out which cl fixed this and merge it back to M70.

tommycli@, please double check and forward to the right owner.

Assigning to Feedback tool owners. Thanks.

No recent changes to the feedback app code that takes a screenshot. I don't develop on Mac, and I won't be able to bisect. Please assign to someone who can.

I just re-tested this on my Macbook Pro and it seems to be working fine on both Canary 71.0.3578.8 as well as Beta 70.3538.54.

So I'm marking this as WONTFIX as I can't reproduce it.

--

That being said, if this issue pops up again, I expect that either braveyao or someone on the Feedback component team to take ownership.

The code I own as referenced in c#3 is the "Report an Issue" string definition.

Both the Feedback component team and the IOSurfaceCapturer owners are more proximate. If the bug is Mac-specific and turning off IOSurfaceCapturer "fixes" the issue, I'm suspecting there is a interaction with IOSurfaceCapturer.

Thanks you all.