1258062 - Cells rendered black with Google sheets

Status: RESOLVED WORKSFORME

(Core :: Graphics, defect)

Description

[Brian Birtles (:birtles, Feb 26~ parental leave)]

Attachment: Screenshot

When using Google sheets on Developer Edition today I see large areas rendered black on certain spreadsheets. See attached screenshot (note that the *grey* areas are just confidential information I blurred out--the *black* areas are as rendered).

It doesn't happen with all spreadsheets, just some. Also, the area that is blacked out changes from time to time (e.g. when resizing the window) but is impossible to remove completely. It doesn't disappear, for example, when I select a black cell (as you can see in the screenshot).

A few items from about:support:

アプリケーション基本情報
------------

名前: Firefox
バージョン: 47.0a2
ビルド ID: 20160312004006
更新チャンネル: aurora
ユーザエージェント: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0
OS: Windows_NT 10.0 x86
マルチプロセスウィンドウ: 0/1 (無効)
セーフモード: false


グラフィックス
-------

Direct2D 有効: true
DirectWrite 有効: true (10.0.10240.16430)
GPU #2 の使用: false
GPU 描画支援のウィンドウ: 1/1 Direct3D 11 (OMTC)
WebGL レンダラ: Google Inc. -- ANGLE (Intel(R) HD Graphics Family Direct3D11 vs_5_0 ps_5_0)
windowLayerManagerRemote: true
アダプタ RAM: Unknown
アダプタドライバ: igdumdim64 igd10iumd64 igd10iumd64 igd12umd64 igdumdim32 igd10iumd32 igd10iumd32 igd12umd32
アダプタ名: Intel(R) HD Graphics Family
サブシステム ID: 00000000
デバイス ID: 0x0a16
ドライバのバージョン: 10.18.15.4256
ドライバの日付: 7-17-2015
ハードウェア H264 デコーディング対応: Yes
ベンダ ID: 0x8086
非同期パン / ズーム: なし
AzureCanvasAccelerated: 0
AzureCanvasBackend: direct2d 1.1
AzureContentBackend: direct2d 1.1
AzureFallbackCanvasBackend: cairo


ロックされた重要な設定
-----------

JavaScript
----------

インクリメンタル GC: true

アクセシビリティ
--------

有効: true
アクセシビリティの無効化: 0


実験的な機能
------

名前: Multi-process Firefox A/B Test
ID: [e-mail]
説明: Measure the effect of multi-process Firefox
アクティブ: false
終了日: 1446353215064
ホームページ:
ブランチ: user-disabled


Let me know if you want anything translated.

Comment 1

[Brian Birtles (:birtles, Feb 26~ parental leave)]

Attachment: Another screenshot

Just applied update and restarted, problem still exists.

Tried to resize window but the problem only becomes worse as evidenced in this screenshot.

Comment 2

[Jamie Nicol [:jnicol]]

Thanks for the report. Are you able to run mozregression to find what introduced this regression? And would you be able to supply a file, scrubbed of confidential information, which can reproduce this?

Comment 3

[Brian Birtles (:birtles, Feb 26~ parental leave)]

(In reply to Jamie Nicol [:jnicol] from comment #2)
> Thanks for the report. Are you able to run mozregression to find what
> introduced this regression? And would you be able to supply a file, scrubbed
> of confidential information, which can reproduce this?

Possibly. This only reproduces on my home machine, and not 100% reliably so it might take some time. I'll give it a try tomorrow.

Comment 4

[Andrew McCreight [:mccr8]]

This might be a long shot, but you should also look at about:memory and check if the memory usage is particularly high. I think that one possible side effect of running low on memory is graphics stuff going weird, and we have a number of bugs on file about high memory usage with Google Sheets (such as bug 1249739).

Comment 5

[Brian Birtles (:birtles, Feb 26~ parental leave)]

Sounds possible although I don't remember memory usage being particularly high on that occasion. I brought my laptop to work to try and repro and run mozregression but was unable to repro. If I hit it again, I'll check memory usage.

Comment 6

[Brian Birtles (:birtles, Feb 26~ parental leave)]

Brought my computer to try reproducing but without any luck. I'll follow up if I manage to repro again.

Comment 7

[Ciprian Muresan [:cmuresan], Ecosystem QA]

Hi,

I have tried to reproduce this issue on the latest Nightly (48.0a1, Build ID 20160328004018) and Aurora (47.0a2, Build ID 20160328004018) and no matter how many times I resize my window, minimize or switch tabs I can't reproduce this issue. 
If you figure out how to reproduce it consistently please add steps to reproduce.

Thanks,
Cipri

Comment 8

[u279076]

I'm closing this since the issue does not appear to be reproducible. Please reopen the bug report if the issue returns.