Closed Bug 1460442 Opened 6 years ago Closed 6 years ago

Crash in static <T> core::result::unwrap_failed<T> | static struct webrender::debug_render::DebugRenderer webrender::debug_render::DebugRenderer::new

Categories

(Core :: Graphics: WebRender, defect, P2)

x86_64
Windows 10
defect

Tracking

()

RESOLVED FIXED
mozilla63
Tracking Status
firefox-esr52 --- unaffected
firefox-esr60 --- unaffected
firefox60 --- unaffected
firefox61 --- disabled
firefox62 --- disabled
firefox63 --- fixed

People

(Reporter: jan, Assigned: nical)

References

(Blocks 1 open bug)

Details

(Keywords: crash, nightly-community)

Crash Data

Seen on Socorro.

> called `Result::unwrap()` on an `Err` value: Compilation("debug_font", "")
https://github.com/servo/webrender/blob/2c57f9400fefa6ddacc6da61ebc57008db6285cc/webrender/src/debug_render.rs#L108

bp-99a4d684-6688-47aa-8185-c055c0180410 build 2018-04-10_100115 Win10
bp-b1b2eb28-3b4b-42b6-8712-c72bd0180509 build 2018-05-07_222648 Win10
bp-e3e6d763-084c-4902-9722-cea290180411 build 2018-04-07_220122 Win10
This is kind of interesting. 13 instances, all in May 2018, all on Windows 10, but on a variety of graphics cards. But all failed to compile the debug_font shader.
Maybe this is a permafail but only happens when the WR profiler is turned on. It doesn't look like the DebugRenderer is used in the normal codepaths.
Assignee: nobody → nical.bugzilla
Status: NEW → RESOLVED
Closed: 6 years ago
Depends on: 1477505
Resolution: --- → FIXED
Target Milestone: --- → mozilla63
You need to log in before you can comment on or make changes to this bug.