ChanServ changed the topic of #zink to: official development channel for the mesa3d zink driver || https://docs.mesa3d.org/drivers/zink.html
illwieckz has quit [Ping timeout: 480 seconds]
kurufu has quit [Read error: Connection reset by peer]
kurufu has joined #zink
Sachiel has quit [Remote host closed the connection]
Sachiel has joined #zink
steven has quit [Quit: ZNC 1.8.2 - https://znc.in]
steven has joined #zink
<daniels> haha
illwieckz has joined #zink
illwieckz has quit [Ping timeout: 480 seconds]
illwieckz has joined #zink
<kusma> zmike: I'm seeing crashes in RADV when running Q3A on top of Zink+RADV, due to what appears to be missing image memory attached to an image view...? Does that ring any bell to you?
<kusma> The code in RADV where this happens does consider some plane-stuff... I also notice that while iview->vk.format VK_FORMAT_B8G8R8A8_UNORM, iview->image->vk.format is 33751040, which seems a bit bonkers...
<kusma> Also other members of iview->image->vk seems... off. Like: extent = {width = 2473000960, height = 55826, depth = 0}, mip_levels = 0, array_layers = 1148846080, samples = 0
<kusma> Valgrind seems to have something to say about the matter: https://gitlab.freedesktop.org/-/snippets/7364
<kusma> That first one is by coincidence very close to where I see the null deref
<kusma> (and with "by coincidence" I mean probably not at all)
<kusma> Also, seems to be the same culprit as the problem I mention here: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20613#note_1732238
<kusma> increasing the refcount of cdt doesn't seem to help :/
<zmike> 🤔 haven't seen before but I can check when I get home if you give me a repro?
<kusma> Just run quake3
<zmike> I don't have quake3?
<kusma> I see... Seems to be the same as the doom3 issue, BTW
<zmike> so I saw
<kusma> I can try to capture the issue on Monday if needed
* zmike prays that an apitrace is enough to trigger doom
<zmike> I've got a doom trace I'll try, if that doesn't work then see if you can get a q3 trace that hits it
<kusma> I guess it's intentional that this is a weak reference? That object is usually recounted...
<zmike> yes it's just used for pointer comparisons
<kusma> But if it's just to keep track of changes, I think it's safe
<kusma> Yeah, exactly
<kusma> I guess we could miss an update if the object gets deleted and then realloced with the same pointer or some garbage like that...
<kusma> That seems extremely unlikely, given that the swapchains kinda live longer than ideal ATM, though
<zmike> dt doesn't get deleted though
<zmike> that's the outer object
<kusma> Aha
<zmike> hm maybe I didn't keep up with the kopper changes as well as I thought
<zmike> yea ok I think I see it
<kusma> Addrefing didn't help for me
<zmike> it wouldn't
<zmike> I think this should do it...
* zmike prays
<zmike> though my doom testing was inconclusive
<kusma> Yeah, that looks likely. I'm out and about to have a few cold ones, but I can test tomorrow.
<zmike> have another cold one for me
<kusma> 🍺
<zmike> 👍
<zmike> these validation errors are actually insane
xperia64 has quit [Quit: WeeChat 3.0]
xperia64 has joined #zink
xperia64 has quit [Remote host closed the connection]
xperia64 has joined #zink