1245971 - painting issues after leaving m-c opened for several days without a restart

Status: RESOLVED WORKSFORME

(Core :: Graphics, defect)

Description

[Kamil Jozwiak [:kjozwiak]]

Attachment: issue1.PNG

After leaving m-c opened for a few days on my Win 10 machine without updating, all the windows start having painting issues when scrolling. Sometimes the windows are restored and sometimes they become completely unusable.. When this happens, m-c becomes really unstable and I usually have to restart/update. I can reproduce this pretty consistently and it happens at least 2-3 times a week when I leave fx opened.

I've attached some images to illustrate the problem. I'll attach the gfx information from that particular machine once I get home.

Comment 1

[Kamil Jozwiak [:kjozwiak]]

Attachment: issue2.PNG

Comment 2

[Kamil Jozwiak [:kjozwiak]]

Attachment: issue3.PNG

Comment 3

[Kamil Jozwiak [:kjozwiak]]

{
  "application": {
    "name": "Firefox",
    "version": "47.0a1",
    "buildID": "20160203030249",
    "userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:47.0) Gecko/20100101 Firefox/47.0",
    "safeMode": false,
    "updateChannel": "nightly",
    "supportURL": "https://support.mozilla.org/1/firefox/47.0a1/WINNT/en-US/",
    "numTotalWindows": 1,
    "numRemoteWindows": 1,
    "remoteAutoStart": true,
    "autoStartStatus": 1
  },
  "graphics": {
    "numTotalWindows": 1,
    "numAcceleratedWindows": 1,
    "windowLayerManagerType": "Direct3D 11",
    "windowLayerManagerRemote": true,
    "supportsHardwareH264": "Yes",
    "adapterDescription": "NVIDIA GeForce GTX 670",
    "adapterVendorID": "0x10de",
    "adapterDeviceID": "0x1189",
    "adapterSubsysID": "26783842",
    "adapterRAM": "2048",
    "adapterDrivers": "nvd3dumx,nvwgf2umx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um,nvwgf2um",
    "driverVersion": "10.18.13.5891",
    "driverDate": "11-5-2015",
    "adapterDescription2": "Intel(R) HD Graphics 4000",
    "adapterVendorID2": "0x8086",
    "adapterDeviceID2": "0x0162",
    "adapterSubsysID2": "0000000c",
    "adapterRAM2": "Unknown",
    "adapterDrivers2": "igdumdim64 igd10iumd64 igd10iumd64 igdumdim32 igd10iumd32 igd10iumd32",
    "driverVersion2": "10.18.10.4276",
    "driverDate2": "8-17-2015",
    "isGPU2Active": false,
    "direct2DEnabled": true,
    "directWriteEnabled": true,
    "directWriteVersion": "10.0.10586.0",
    "webglRenderer": "Google Inc. -- ANGLE (NVIDIA GeForce GTX 670 Direct3D11 vs_5_0 ps_5_0)",
    "info": {
      "AzureCanvasBackend": "direct2d 1.1",
      "AzureSkiaAccelerated": 0,
      "AzureFallbackCanvasBackend": "cairo",
      "AzureContentBackend": "direct2d 1.1",
      "ApzWheelInput": 1,
      "ApzTouchInput": 1
    }
  }
}

Comment 4

[u279076]

Kamil, have you seen this recently?

Comment 5

[Kamil Jozwiak [:kjozwiak]]

(In reply to Anthony Hughes (:ashughes) [GFX][QA][Mentor] from comment #4)
> Kamil, have you seen this recently?

I haven't seen this in a long time. I left my m-c instance running on my desktop machine for about 7 days now and haven't ran into this. The issue I described would often happen after 2-3 days of not restarting m-c so I'm pretty sure this was fixed somewhere along the way.