четвер, 8 лютого 2018 р. 12:20:29 EET Michal Srb написано:
On čtvrtek 8. února 2018 11:10:16 CET Mykola Krachkovsky wrote:
четвер, 8 лютого 2018 р. 11:53:12 EET Michal Srb написано:
On čtvrtek 8. února 2018 10:43:25 CET Mykola Krachkovsky wrote: But why previous (buggy) version worked fine? That's strange. My Mesa updates: 2018-02-01 11:35:16|install|Mesa|17.3.3-184.1|x86_64||openSUSE-20170510-0| 006a8dca9246bf852111f7fcee1f34d301a0252c| 2018-02-05 16:47:28|install|Mesa|18.0.0-185.1|x86_64||openSUSE-20170510-0| 6c4c429c5eb872737d7453cc0ed711ff455de424| 2018-02-08 09:45:27|install|Mesa|18.0.0-187.1|x86_64||repo-update| 7f37602bf8aa77467c45fb470c97f8f9dc26e78a78d9512e01405003c4887123|
It all just depends on how long you were using the broken version.
The path to get damaged cache with the broken Mesa was:
Compile shader -> store to cache -> load from cache -> store to cache.
During this chain of events the shader was still good and useable. Only the next load from cache with ANY version of Mesa results in invalid shader and broken rendering.
So maybe you never got to the second load from cache while you had the broken version. Only after updating to the next version and rebooting it happened.
Michal
Well, between 2018-02-05, 18.0.0-185.1 (I expect that's a broken version, isn't it?) and today (2018-02-08, 18.0.0-187.1) I definitely rebooted several times (at least 3 times). I almost never use suspend to disk, so usually just switch off and back on the pc. -- Kind regards, Mykola Krachkovsky -- Найкращі побажання, Микола Крачковський