News for hackers. Stuff that matters.
Re:Firefox 64 Released by shmerl on Tuesday December 11, 2018 @02:31PM (#18658074)
I've just updated to new beta (Firefox 65.0b3) with WebRender enabled and it started showing such error in about:support:

    [GFX1-]: shader-cache: Shader disk cache is not supported
I'm using AMD GPU and as far as I know, Mesa supports shader cache for radeonsi and radv.

Does anyone know why that error is showing up?

Re:Firefox 64 Released by bholley on Tuesday December 11, 2018 @03:22PM (#18658521)
See https://bugzilla.mozilla.org/show_bug.cgi?id=1511726

Assuming you're on non-Windows, the message is expected and not indicative of a problem. I've pushed a patch to disable it going forward. Sorry for the noise.

Re:Firefox 64 Released by shmerl on Tuesday December 11, 2018 @03:40PM (#18658643)
Thanks for the pointer. May be still display something but like "shader cache is not used" so it will be clear that the feature isn't utilized yet.
Re:Firefox 64 Released by bzbarsky on Tuesday December 11, 2018 @02:49PM (#18658237)
This is talking about webrender's on-disk shader cache for the shaders it itself is deciding to cache, not your GPU driver's shader cache.

Looking at https://searchfox.org/mozilla-central/rev/adcc169dcf58c2e45b... it looks like that error means the disk cache was not created.

So either get_cache_path_from_prof_path failed to return a path or create_dir_all failed.

I haven't dug through more details, but I'm pretty sure the shader cache code there is new and am not at all sure it's completely hooked up yet.

Re:Firefox 64 Released by samirm on Tuesday December 11, 2018 @02:33PM (#18658108)
because you're on a beta build?
Re:Firefox 64 Released by shmerl on Tuesday December 11, 2018 @02:41PM (#18658180)
Why would beta build not find shader cache?
Re:Firefox 64 Released by jjuhl on Tuesday December 11, 2018 @03:00PM (#18658356)
Beta == unfinished, may have bugs.
Re:Firefox 64 Released by pbhjpbhj on Tuesday December 11, 2018 @05:25PM (#18659566)
No, "beta" means "finished, but may have non-show-stopper bugs".

If it's not finished it's alpha.

Beta is pretty much just used as "buyer beware" nowadays, like a disclaimer "we take no responsibility for our bugs".

Re:Firefox 64 Released by JohnFen on Tuesday December 11, 2018 @06:16PM (#18659896)
Offtopic for sure, but the way most places I've worked have used the terms is: "alpha" means that the developers think it's done. "beta" means QA thinks it's done. "release" means that actual user testing revealed no showstoppers.