Alpha 25b Crashes on Startup. No Errors.

[Steve]

Hi,

Alpha 25b crashes on startup with no errors.

Windows 11
13th Gen Intel(R) Core(TM) i9-13900K 3.00 GHz
32.0 GB RAM
NVIDIA GeForce RTX 3070

Regards,

Steve

[peterigz]

Thanks for the report, are you extracting zip first before running the Exe? And is the location writable? You could try running as administrator maybe.

Do you know what driver version you have? Unlikely to be the issue but you ever know. Oh and did previous versions work or is this the first version you tried?

In the next alpha I’ll have more logging for crashes like this to help track things down. I can test locally on amd and intel cpus with amd 6600, nvidia 1660 and a very cheap nvidia 710 gpus so in theory your system should be fine.

[Steve]

Hi Peter,

Yes, I’m extracting all of the files before running it. I tried running as administrator but still get the same result.

I have checked the permissions and they are correct.

The Dec 2023 versions doesn’t work either, but versions prior to that are fine. It tries to start up. I get a blank window that sits there for a couple of seconds and then disappears.

The NVIDIA driver version is 31.0.15.3619.

I turned the anti-virus software off but that didn’t make a difference.

= Steve

[peterigz]

Thanks, I have an inkling as to what it could be, but either way will have more logging in the next version.

[Steve]

No worries. More logging sounds like a good idea.

= Steve

[peterigz]

I have uploaded a new version with a potential fix but it’s kind of a guess. Either way, when you run this version it should save a zest_log.txt in the same folder so if it crashes then copy and paste that log here and I can get some more clues. Thanks!

Download: https://www.rigzsoft.co.uk/files/TimelineFXAlpha.zip

[Steve]

Thanks. Unfortunately that didn’t work either.

Here is the zest log:

Start of Log
Create window with dimensions: 2560, 1369
Extension: VK_KHR_surface
Extension: VK_KHR_win32_surface
Validating Vulkan Instance
Found suitable device
Graphics queue index set to: 0
Compute queue index set to: 2
Transfer queue index set to: 1
Creating logical device
Creating command queues
Set device pool sizes
Create swap chain
Create swap chain image views
Create standard render passes
Create depth passes
Create swap chain frame buffers
Create sync objects
Create descriptor pools
Create descriptor layouts
Create pipeline cache
Create standard pipelines
2d sprites pipeline
2d sprites alpha pipeline
SDF Lines pipeline
Font pipeline
Billboard pipeline
Billboard alpha pipeline
ImGui pipeline
Mesh pipeline
Final render pipeline
Fatal : VkResult is ” ERROR_OUT_OF_DEVICE_MEMORY ” in E:\Projects\C++\TimelineFX\TFXEditor\submodules\zest\zest.c at line 2014

[peterigz]

oh interesting, that is definitely not what I would have expected 😀

Ok thanks I can start pondering what might cause that, obviously your gpu has plenty of memory.

[peterigz]

I uploaded a new version, thanks for helping to test, appreciate it! https://www.rigzsoft.co.uk/files/TimelineFXAlpha.zip

I added in a few more logs and changed how it picks the device. I thought that maybe if you have an integrated gpu on the motherboard that maybe it was picking that over the discrete GPU ie. the 3070. So this will prioritise the discrete GPU instead. But at least we’ll see what’s being picked and also more memory logging.

[Steve]

I’m happy to help test.

Unfortunately, still crashes on startup.

Start of Log
Create window with dimensions: 2560, 1369
Extension: VK_KHR_surface
Extension: VK_KHR_win32_surface
Validating Vulkan Instance
Found 2 devices
NVIDIA GeForce RTX 3070
Intel(R) UHD Graphics 770
Found suitable device that is a discrete GPU: NVIDIA GeForce RTX 3070
Memory available in GPU:
Heap flags: 1, Size: 8422162432
Heap flags: 0, Size: 17016672256
Heap flags: 1, Size: 224395264
Graphics queue index set to: 0
Compute queue index set to: 2
Transfer queue index set to: 1
Creating logical device
Creating command queues
Set device pool sizes
Create swap chain
Create swap chain image views
Create standard render passes
Create depth passes
Create swap chain frame buffers
Create sync objects
Allocating memory pool, size: 1048576 type: 2, alignment: 64, type bits: 31
Create descriptor pools
Create descriptor layouts
Create pipeline cache
Create standard pipelines
2d sprites pipeline
2d sprites alpha pipeline
SDF Lines pipeline
Font pipeline
Billboard pipeline
Billboard alpha pipeline
ImGui pipeline
Mesh pipeline
Final render pipeline
Allocating memory pool, size: 33554432 type: 2, alignment: 4, type bits: 31
Allocating memory pool, size: 4194304 type: 4, alignment: 16, type bits: 31
Fatal : VkResult is ” ERROR_OUT_OF_DEVICE_MEMORY ” in E:\Projects\C++\TimelineFX\TFXEditor\submodules\zest\zest.c at line 2063

[peterigz]

Perfect thanks. Do you know what driver version you currently have? Oh nm, you gave driver version above, thanks.

I’ve got a feeling I know what the issue is just looking more into it.

• This reply was modified 8 months, 2 weeks ago by peterigz.

[peterigz]

Another version here: https://www.rigzsoft.co.uk/files/TimelineFXAlpha.zip

This should provide more hints in the logs and also a potential fix, but we’ll see. It would also be interesting if you could update your drivers to the latest version as it may well be a driver bug as well. I don’t recognise your driver version, they seem to be in a different format on the nvidia site when I try and search here: https://www.nvidia.com/Download/Find.aspx?lang=en-us where the version numbers are in the format 551.76. It would have been interesting to install your driver version to see if I could recreate the bug here. Thanks!

[Steve]

When I go to update it says that I have the latest version. Could it be different because it’s a Dell machine?

Here’s the latest log:

Start of Log
Create window with dimensions: 2560, 1369
Extension: VK_KHR_surface
Extension: VK_KHR_win32_surface
Validating Vulkan Instance
Found 2 devices
NVIDIA GeForce RTX 3070
Intel(R) UHD Graphics 770
Found suitable device that is a discrete GPU: NVIDIA GeForce RTX 3070
Memory available in GPU:
Heap flags: 1, Size: 8422162432
Heap flags: 0, Size: 17016672256
Heap flags: 1, Size: 224395264
Memory types mapping in GPU:
0) Heap Index: 1, Property Flags: 0
1) Heap Index: 0, Property Flags: 1
2) Heap Index: 1, Property Flags: 6
3) Heap Index: 1, Property Flags: 14
4) Heap Index: 2, Property Flags: 7
Graphics queue index set to: 0
Compute queue index set to: 2
Transfer queue index set to: 1
Creating logical device
Creating command queues
Set device pool sizes
Create swap chain
Create swap chain image views
Create standard render passes
Create depth passes
Allocating image memory pool, size: 67108864 type: 1, alignment: 1024, type bits: 3
Create swap chain frame buffers
Create sync objects
Allocating buffer memory pool, size: 1048576 type: 2, alignment: 64, type bits: 31
Create descriptor pools
Create descriptor layouts
Create pipeline cache
Create standard pipelines
2d sprites pipeline
2d sprites alpha pipeline
SDF Lines pipeline
Font pipeline
Billboard pipeline
Billboard alpha pipeline
ImGui pipeline
Mesh pipeline
Final render pipeline
Allocating buffer memory pool, size: 33554432 type: 2, alignment: 4, type bits: 31
Allocating image memory pool, size: 67108864 type: 1, alignment: 1024, type bits: 3
Allocating image memory pool, size: 67108864 type: 1, alignment: 1024, type bits: 3
Allocating image memory pool, size: 67108864 type: 1, alignment: 1024, type bits: 3
Allocating image memory pool, size: 67108864 type: 1, alignment: 1024, type bits: 3
Creating Device local buffers for sprite layer
Allocating buffer memory pool, size: 4194304 type: 4, alignment: 16, type bits: 31
Creating Device local buffers for mesh layer
Allocating buffer memory pool, size: 4194304 type: 4, alignment: 4, type bits: 31
Fatal : VkResult is ” ERROR_OUT_OF_DEVICE_MEMORY ” in E:\Projects\C++\TimelineFX\TFXEditor\submodules\zest\zest.c at line 2067

[peterigz]

Yes it could well be, I did notice references to dell machines when I googled it. Thanks again for the logs.

I’m fairly certain that it’s to do with it “Creating local buffers for sprite/mesh other layers” which is something I started doing to fix a separate issue on AMD cards. The strange thing is that it’s trying to allocate that memory from the heap that has ~224mb but it’s only trying to allocate 4mb. My nvidia 1660 has almost the same logs but it works fine, it makes me feel like it’s a driver bug. However what I think I’ll do is just disable that on nvidia cards and hopefully that should do it.

[Steve]

Interesting. I’ll check the Dell Update software to see if there are any updates.

I’m happy to test anything that you want tested.

[Author]

Posts