Command stream queues are implemented using a fixed size array. This implementation requires NOP packets to be inserted at the end sometimes, so that these packets can be skipped and the head pointer can be properly move back to the beginning. Furthermore, sometimes it is necessary to insert padding packets that contain zero data (besides the size field), so they don't even have space for the NOP opcode. Their opcode shouldn't be read. Currently it is possible to get trace messages such as this: 0484:trace:d3d:wined3d_cs_queue_submit Queuing op UNKNOWN_OP(0x34) at 06EF1C8C. for these padding packets. In this case the packet was from cs->queue[0] but 0x34 was actually cs->queue[1].size. Depending of the out-of-bounds data, spurious yet valid opcodes could be reported, so we fix that. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9903