LUMIERA.clone/tests/core/steam
Ichthyostega 9a23aa773b Invocation: analyse usage of buffer metadata entries
Code clean-up: mark all buffers with a dedicated tagging type


The point in question is: if we work the LocalTag into the type-hash,
could it be possible to miss an existing entry in the metadata registry?
This could cause two entries to be locked for a single buffer address,
leading to data corruption.

As far as I can see, in the current usage this would not happen,
but unfortunately this problem can not be ruled out, since the BufferProvider
API and protocol is designed to be open for various usage patterns.

However, the same potentially disastrous pattern could also materialise
when registering two different buffer types, and then locking each
for the same buffer location.
2024-07-28 19:29:27 +02:00
..
asset Library: uniform definition scheme for error-IDs 2024-03-21 19:57:34 +01:00
control Library: uniform definition scheme for error-IDs 2024-03-21 19:57:34 +01:00
engine Invocation: analyse usage of buffer metadata entries 2024-07-28 19:29:27 +02:00
fixture Scheduler: devise the arrangement of basic components 2023-06-24 03:14:17 +02:00
mobject Library: uniform definition scheme for error-IDs 2024-03-21 19:57:34 +01:00
play Invocation: clarify role of Buffer-Descriptor and Dependency-Injection 2024-07-15 18:52:59 +02:00
render-segment-test.cpp Dispatcher-Pipeline: prepare test for the new NodeGraphAttachment 2023-06-07 04:03:00 +02:00