Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR: Consuming pipeline libraries while creating a pipeline library #209

Open
mbriar opened this issue Nov 23, 2022 · 2 comments
Open

Comments

@mbriar
Copy link

mbriar commented Nov 23, 2022

Hey, while messing around with the UE5 RT Demo app from HansKristian-Work/vkd3d-proton#1295, I encountered a crash in RADV's shader compiler when the app is run with VKD3D_FEATURE_LEVEL=12_2 VKD3D_CONFIG=dxr11 RADV_PERFTEST=rt.
I wanted to record a fossilize archive to reproduce the crash with FOSSILIZE_DUMP_SYNC=1, but when replaying the generated archive, the compiler crash is not reproduced and I get the following errors:

Fossilize ERROR: Consuming pipeline libraries while creating a pipeline library. This cannot work.
Fossilize WARN: Did not replay blob (tag: 9, hash: 0x046ff16dd2c9efa6). See previous logs for context.
Fossilize ERROR: Consuming pipeline libraries while creating a pipeline library. This cannot work.
Fossilize WARN: Did not replay blob (tag: 9, hash: 0x57ab729c726f4ddd). See previous logs for context.
Fossilize ERROR: Consuming pipeline libraries while creating a pipeline library. This cannot work.
Fossilize WARN: Did not replay blob (tag: 9, hash: 0x046ff16dd2c9efa6). See previous logs for context.
Fossilize ERROR: Consuming pipeline libraries while creating a pipeline library. This cannot work.
Fossilize WARN: Did not replay blob (tag: 9, hash: 0x57ab729c726f4ddd). See previous logs for context.

I'm not sure whether this is a vkd3d-proton or fossilize issue, so reporting it here first.
Relevant foz archive: rttest.d895ec754bd56a9e.2.zip

@HansKristian-Work
Copy link
Collaborator

Pipeline libraries can currently only be replayed with depth of 1. Chained dependencies are extremely awkward to support. At the time, it was not clear if this was even legal (but it is ...).

@mbriar
Copy link
Author

mbriar commented Nov 23, 2022

Sounds like it will be hard to fix. I will report the RADV crash without a foz archive then, should still be easy enough to reproduce with the Demo app, thanks for the quick response 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants