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

Issue 741306 link

Starred by 9 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Jul 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

All ARC app windows are black.

Project Member Reported by kinaba@chromium.org, Jul 12 2017

Issue description

All ARC app windows are black.

On Chrome OS + ToT Chrome. Bisection pointed out:

(sdk veyron_minnie R61-9608.0.0) kinaba@kinaba /ssd/chrome/src $ git bisect bad
c3dec2b9fe8e3e3008b75ee9d8b67229fafc0b34 is the first bad commit
commit c3dec2b9fe8e3e3008b75ee9d8b67229fafc0b34
Author: David Reveman <reveman@chromium.org>
Date:   Wed Jul 12 01:19:11 2017 +0000

    gpu: Fix FD leak when importing DMA-bufs with multiple FDs.
    
    CreateFromHandle is expected to take ownership of all FDs so
    when passed multiple FDs we need to make sure they are closed
    if not used.
    
    BUG=b/63409814
    TEST=exo_unittests --gtest_also_run_disabled_tests --gtest_filter=DisplayTest.DISABLED_CreateLinuxDMABufBuffer
    
    Change-Id: I2a8a7b0149a08f08890a725c6ce9aff8aeaab97f
    Reviewed-on: https://chromium-review.googlesource.com/566879
    Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
    Commit-Queue: David Reveman <reveman@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#485761}
 

Comment 1 by kinaba@chromium.org, Jul 12 2017

Wrote a fix: https://chromium-review.googlesource.com/c/566740



Though, if anyone thinks it urgent I don't object reverting asap for now.

Comment 2 by kinaba@chromium.org, Jul 12 2017

Status: Fixed (was: Assigned)
David reverted the original patch.
https://chromium-review.googlesource.com/c/566863/

Comment 3 by kinaba@chromium.org, Jul 13 2017

Reland. Hope it goes well
https://chromium-review.googlesource.com/c/566960/
Labels: -Type-Bug ReleaseBlock-Dev M-61 Type-Bug-Regression
reprod on Chrome OS 9740.0.0, 61.0.3155.0
Neither the revert (https://chromium-review.googlesource.com/c/566863/) nor the reland (https://chromium-review.googlesource.com/c/566960/) are in Chrome 61.0.3155.0.

The revert should be in Chrome 61.0.3156.0 [1] but the reland didn't quite make it in for that Chrome version - I'd expect it to be in 61.0.3157.0 (not yet tagged...).

Also, Chrome PFQ hasn't rolled ChromeOS to 61.0.3156.0 just yet.

[1] https://chromium.googlesource.com/chromium/src/+log/61.0.3155.0..61.0.3156.0?pretty=fuller&n=10000
The bug seems to be resolved in 61.0.3156.0, but it comes back on ToT.
Status: Assigned (was: Fixed)
re-open it for investigation.

Comment 8 by zalcorn@google.com, Jul 14 2017

Cc: keta...@chromium.org
We also have a canary for 61.0.3158 now, in case we were waiting for the change to propagate.
Cc: hidehiko@chromium.org khmel@chromium.org
+ARC constables, see also b/63667627 
I've been using 61.0.3158.0 and have not seen this issue. 
Cc: allendam@chromium.org
Still seen this issue on Chrome OS 9752.0.0, 61.0.3159.0
Cc: pucchakayala@chromium.org songsuk@chromium.org ajha@chromium.org kavvaru@chromium.org brajkumar@chromium.org dsunk...@chromium.org
 Issue 744235  has been merged into this issue.
I'm seeing black apps in ToT too now but reverting https://chromium-review.googlesource.com/c/566960/ doesn't solve it so this is a different issue.
Status: Fixed (was: Assigned)
Did bisection and hit  http://crbug.com/731742#c7 .
So, the current issue is different from the original one and the original one is fixed. Closing.

There's already an internal bug b/63667627 for the second breakage. Let's use the bug for the new regression. (and file a new Chromium bug when needed)
Verified on kevin 9756.1.0/ 61.0.3159.8 but not fixed on 9759.0.0/61.0.3160.0
Tested on Chrome:61.0.3160.0/9760.0.0 cave but its not fixed.
attached screenshots.
Screenshot 2017-07-19 at 14.13.56.png
1.8 MB View Download
Screenshot 2017-07-19 at 14.13.19.png
46.0 KB View Download
See #17, 61.0.3158.0 or above have a different bug ( Bug 744235 ), not this one.
Fix for this bug can be verified using 61.0.3157.0 (9745.0.0).
Status: Verified (was: Fixed)
Verified on ChromeOS 9765.0.0, 61.0.3162.0

Sign in to add a comment