Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Is it possible for multiple queues to share resources?

Open
#905 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp

Research direction

The issue names MiniEngine's CommandContext, linear allocators, dynamic descriptor heaps, and fence handling, but no repository file or test. Start by locating those components and their queue/resource lifetime logic; done would require a documented, project-specific answer about shared resources across DirectX12 command queues.

Written by the indexing model from the issue text.

Description

In MiniEngine, I observed that resources such as descriptor heaps, buffers, etc. are managed by CommandContext of a specific command list type. In fact, linear allocators, dynamic descriptor heaps, etc. also reclaim resources based on the Fence value of a specific command queue.
When building DirectX12 applications, is it possible that different types of command queues access the same resource? Or are the resources of different command queues usually managed separately?

Dominant language
C++
Stars
6.8k
Forks
2.2k
Avg merge
3d 3h
Merged PRs (30d)
3

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/DirectX-Graphics-Samples

All issues in microsoft/DirectX-Graphics-Samples

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.