[11:23] <lissyx> seb128, bandali, not sure if you saw but glandium got a stack and the PGO crash is because of a (looks to be fixed) use-after-free issue on mesa driver
[11:37] <seb128> lissyx, hey, I saw, I dispatched a test build using proposed on launchpad a bit earlier to see how that works
[11:37] <lissyx> seb128, is this the one glandium saw?
[11:37] <seb128> lissyx, I'm a bit puzzle on why that only started being an issue recently though
[11:37] <seb128> lissyx, the one what?
[11:42] <seb128> lissyx, I don't really understand glandium's comment / how he tested a built against the proposed version, but I expect my 'build against proposed' isn't going to work because it's using the gnome sdk providing libraries and not the ubuntu archive deb
[11:55] <lissyx> seb128, I dont know why it started now, maybe another system lib changed triggering a different code path
[11:55] <lissyx> seb128, for sure latest green build is not green anymore
[11:55] <seb128> lissyx, but that might be another issue with snapcraft what you said right?
[11:55] <lissyx> seb128, also it might be time to revisit the "unset SNAP_INSTANCE_NAME" as part of all my tests I did some with this removed and it was looking to work
[11:57] <seb128> ack
[13:32] <bandali> hey lissyx yeah i came to the same conclusion with my same test builds: removing 'unset SNAP_INSTANCE_NAME', the nightly snap build passed
[13:33] <bandali> i'd actually written to the list about removing that a few months ago, but it somehow fell off my radar and was never done
[13:33] <bandali> i guess now's the time to do it :-)