« Last post by spasi on December 29, 2018, 13:47:13 »
There's MemoryUtil.memReport but it has limitations: it only tracks allocations via MemoryUtil and Configuration.DEBUG_MEMORY_ALLOCATOR must be enabled. There's overhead, so it's not enabled by default. A custom solution would be better if you need memory tracking in release builds.
« Last post by XenoAmess on December 29, 2018, 12:27:39 »
I'm developing a game and I planned to do some garbage collection when I am holding some size of memories with org.lwjgl.BufferUtils in total,like, 4G or so, then I can just find some latest unused textures and delete them. So, I will be super happy if there be some way to get the total size of holding buffers which is allocated by org.lwjgl.BufferUtils. Or should I track it myself?
« Last post by KaiHH on December 29, 2018, 10:34:46 »
I've fixed and rebuilt the shaders which made the demos work again. When enabling validations, there are however some vkCmdPipelineBarrier() errors, which do not seem to have any effect on the rendering however.
« Last post by spasi on December 28, 2018, 23:34:48 »
I tried the demos earlier and could reproduce the crashes. Enabling the Vulkan SDK validation layers (with -Dvulkan.validation=true) seems to indicate an issue with the included SPIR-V modules. Asked httpdigest (the maintainer of lwjgl3-demos) and he mentioned that the shaders were compiled 3 years ago and a recompilation may resolve the issue.
« Last post by Clancy on December 28, 2018, 10:19:59 »
All the Vulkan demos fail in a manner like this using Vulkan 188.8.131.52:
# # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000072697a36, pid=31280, tid=31140 # # JRE version: Java(TM) SE Runtime Environment (10.0.1+10) (build 10.0.1+10) # Java VM: Java HotSpot(TM) 64-Bit Server VM (10.0.1+10, mixed mode, tiered, compressed oops, g1 gc, windows-amd64) # Problematic frame: # C [nvoglv64.dll+0xb07a36] # # No core dump will be written. Minidumps are not enabled by default on client versions of Windows # # An error report file with more information is saved as: # D:\Workspaces\LWJGL\hs_err_pid31280.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. #