Hi Donnie,
The log file looks pretty normal except that everything looks like it took quite a long time, even just starting up, and that doesn't involve a whole lot other than loading some images for the fonts and allocating some memory, which should be rather instantaneous. It almost seems like Windows was not happy at all. I mean, REALLY unhappy, and this wasn't the case with v1.14a? I'm going to put v1.14a up as a complete self-contained zip (instead of an update to v1.13a) which I'm assuming you didn't have problems with, and I want you to test that just so we can make sure it's specific to v1.15a.
Just off the top of my head, do you restart your computer often or just let it sleep when you're not using it (and it hasn't been fully rebooted in a while)? I almost never reboot my machines, unless it starts causing problems (which it does) and I've seen it cause problems like this before once in a blue moon. If you don't usually reboot your machine regularly could I suggest trying that? The log is showing that the simplest actions are taking an unusually extreme amount of time to complete, which has me leaning more toward it being a system-related issue. Perhaps there's some kind of software that is running in the background hogging resources, or Windows is just clogged up from being up for too long without a reboot? I'm somewhat at a loss here. I feel like I've seen something like this before, and it was a cache-related issue but it involved there being many calculations per program frame. In this instance PixelCNC isn't even doing anything and it's going really slow.
The only other thing I can think is that the SDL dll files PixelCNC v1.15a is using are different, which are used for support functions, like loading images and dealing with creating a window and gathering user input. If v1.14a runs fine but v1.15a does not then I think it's safe to say that they are the problem, which leaves my hands somewhat tied if I want to keep SVG support the way it is right now. I could likely find a different route, but ideally SDL would just work the way it's meant to across all Windows systems.
I can only suggest doing a reboot and then running PixelCNC, because I don't see any problems on any of my machines, and I'm running Windows 7, 8.1, and 10 across 5 different machines that don't exhibit the symptoms you're experiencing. I am almost thinking it's something like a program updating itself, maybe even Windows itself, unless it's the SDL dlls. If you're running an antivirus you could try temporarily disabling that and running v1.15a too I suppose.
What are your system specs? CPU, memory, graphics card/GPU, Windows version? This information may help lead us get to the solution.
Go ahead and download v1.14a and unzip that to a separate folder, and see if that still runs fine for you. If it does, try v1.15a again. The goal is to determine if it's a system thing or unique to something that has changed between v1.14a and v1.15a.