Vulkan API Layer
active 2024-08-13 → 2025-12-16 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 491 days from 2024-08-13 to 2025-12-16. Pushes: 17 total, peak 6 in a day. Pull requests: 3 total, peak 1 in a day. Issues: 8 total, peak 2 in a day. Comments: 8 total, peak 1 in a day. Stars: 13 total, peak 1 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
Recent activity
Latest issues, pull requests and releases
- Issue comment#183jinjianrong2025-09-15 03:30Fix implementation of VK_EXT_depth_clamp_control
- Pull request#183CrossVR2025-08-03 01:10
- Issue#182CrossVR2025-07-29 10:02`VK_EXT_depth_clamp_control` is incorrectly implemented
- Issue comment#63Hineven2025-03-29 08:46vkResetCommandPool slower than recreating, regardless of TRANSIENT_BIT
- Issue comment#179kleinerm2024-11-06 01:51AMDVLK out of bounds write causes memory corruption/crash when an attached display monitor has more than 64 video modes.
- Issue comment#179kleinerm2024-11-04 00:13AMDVLK out of bounds write causes memory corruption/crash when an attached display monitor has more than 64 video modes.
- Issue comment#179jinjianrong2024-11-03 23:52AMDVLK out of bounds write causes memory corruption/crash when an attached display monitor has more than 64 video modes.
- Issue#179kleinerm2024-11-02 22:41AMDVLK out of bounds write causes memory corruption/crash when an attached display monitor has more than 64 video modes.
- Issue#179kleinerm2024-11-02 21:07AMDVLK out of bounds write causes memory corruption/crash when an attached display monitor has more than 64 video modes.
- Issue comment#178jinjianrong2024-10-31 05:42`vkGetPhysicalDeviceImageFormatProperties` does not take into account `VK_IMAGE_CREATE_BLOCK_TEXEL_VIEW_COMPATIBLE_BIT`
- Issue#178jinjianrong2024-10-31 05:42`vkGetPhysicalDeviceImageFormatProperties` does not take into account `VK_IMAGE_CREATE_BLOCK_TEXEL_VIEW_COMPATIBLE_BIT`
- Pull request#177jinjianrong2024-10-30 03:38
- Issue#179kleinerm2024-10-01 05:10AMDVLK out of bounds write causes memory corruption/crash when an attached display monitor has more than 64 video modes.
- Issue#178Macdu2024-09-21 11:05`vkGetPhysicalDeviceImageFormatProperties` does not take into account `VK_IMAGE_CREATE_BLOCK_TEXEL_VIEW_COMPATIBLE_BIT`
- Issue comment#106jinjianrong2024-08-20 06:32Invalid unit in VkPipelineCreationFeedbackEXT::duration on Windows
- Issue#106jinjianrong2024-08-20 06:32Invalid unit in VkPipelineCreationFeedbackEXT::duration on Windows
- Pull request#177qiaojbao2024-08-16 08:15
- Issue comment#173jinjianrong2024-08-14 02:03vkQueueSubmit2 does not respect VkCommandBufferSubmitInfo::deviceMask
- Issue#173jinjianrong2024-08-14 02:03vkQueueSubmit2 does not respect VkCommandBufferSubmitInfo::deviceMask
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 13 stars here means stars gained during the window, not the repo's star count.