Closed
Bug 1395238
Opened 7 years ago
Closed 7 years ago
Stop trying to get device statuses in content
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
firefox57 | --- | affected |
People
(Reporter: Alex_Gaynor, Unassigned)
References
Details
(Whiteboard: gfx-noted)
As a part of the win32k lockdown research work, I've identified the following stack, which uses win32k:
win32u!NtGdiDdDDIGetDeviceState
d3d11!CDevice::GetDeviceRemovedReason+0x83
xul!mozilla::gfx::DidDeviceReset+0x1d
xul!mozilla::gfx::DeviceManagerDx::GetAnyDeviceRemovedReason+0x2c
xul!mozilla::gfx::DeviceManagerDx::HasDeviceReset+0x59
xul!gfxWindowsPlatform::SchedulePaintIfDeviceReset+0x45
xul!nsRefreshDriver::Tick+0x226
xul!mozilla::RefreshDriverTimer::TickDriver+0x53
xul!mozilla::RefreshDriverTimer::TickRefreshDrivers+0x5a
xul!mozilla::RefreshDriverTimer::Tick+0xcf
xul!mozilla::VsyncRefreshDriverTimer::RunRefreshDrivers+0x84
xul!mozilla::VsyncRefreshDriverTimer::RefreshDriverVsyncObserver::TickRefreshDriver+0xce
xul!mozilla::VsyncRefreshDriverTimer::RefreshDriverVsyncObserver::NotifyVsync+0x124
xul!mozilla::layout::VsyncChild::RecvNotify+0x5a
xul!mozilla::layout::PVsyncChild::OnMessageReceived+0x223
xul!mozilla::ipc::PBackgroundChild::OnMessageReceived+0x4f
It looks like this is related to checking for hardware device support -- this should always be done in the parent process.
Updated•7 years ago
|
Whiteboard: gfx-noted
Comment 2•7 years ago
|
||
(In reply to Peter Chang[:pchang] from comment #1)
> Vincent, could you take a look?
Ok. I will take a look into it.
Comment 3•7 years ago
|
||
(In reply to Vincent Liu[:vliu] from comment #2)
> (In reply to Peter Chang[:pchang] from comment #1)
> > Vincent, could you take a look?
>
> Ok. I will take a look into it.
Based on the discussions in bug 1395315, I will set WONTFIX. Please change it if anyone has different opinion. Thanks.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Updated•7 years ago
|
Flags: needinfo?(vliu)
Reporter | ||
Comment 4•7 years ago
|
||
I'd like to keep this open, even if it's a low priority for the graphics team; this is a blocker for accomplishing the win32k lockdown work that is on the sandboxing roadmap, and I don't want to lose track of it.
You need to log in
before you can comment on or make changes to this bug.
Description
•