i’d be glad to help diagnose this issue. please let me know if there is any more information i can provide or tests i can run to help in finding a solution. I’ve checked the logs in AppData/Roaming/com.juce.projucer and nothing is helpful in the compiler logs, but the IDE logs have a line with:
This should be fixed with the release of 5.1.1 today. If you’re using the prebuilt Projucer binary downloaded from the JUCE website it will have the new live-build engine embedded already but if you are building the Projucer yourself you’ll need to delete the old dll and download the new one - this post explains how to do that.
Hi, Same issue here, VS2017, Win10 x64 15063.483
I have built V5.1.1 and downloaded latest compilation engine dll
but I still get the “JIT process stopped responding” whenever I try to run a component.
I’ll try to install VS2015 side by side to see whether I can workaround on this for the time being.
If is there anything I can try to help pinpoint the issue let me know,
This thread seems to be a couple of months old now, but I’ve just started to experience this issue and it’s doing my head no good. I’m running Visual Studio Community 2017 v15.5.2, JUCE v5.2.0 on a Windows 10 machine. The JIT engine just keeps crashing giving the message “JIT process stopped responding!” This only seems to be the case for the 10.0.16299.0 and 10.0.14393.0 Platform Targets. With earlier targets JIT runs fine, but then I have multiple missing header errors instead. Linking to the relevant kit (C:\Program Files (x86)\Windows Kits\10\Include\ … ) in System Header Paths doesn’t fix either issue, and neither does deleting the JUCECompileEngine.dll and letting the Projucer reinstall it. I’ve literally tried every combination of Toolset and Target Platform for VS2017 and VS2015 with the same result, either a JIT failure or missing headers. I also tried to export to Codeblocks as a last resort but with a similar JIT failure. What I did notice is that the Projucer flies upto 100% CPU just before the JIT crash in Task Manager. Any help would be very welcome!
Just a quick bump on this thread as I’ve tried a few things to no avail.
I’ve just completed a complete system reset, so I have a fresh and clean install of the latest version of Windows 10, fully updated along with all of my drivers. I have installed the latest version of Visual Studio 2017 Community, with just the Desktop Development with C++ Workload installed. I have also installed various toolsets from the list: Windows 8.1 SDK and UCRT SDK; Windows 10 SDK (10.0.16299.0); Windows 10 SDK (10.0.15063.0); Windows 10 SDK (10.0.10240.0); VC++ 2015.3 v140 toolset. I’m also running JUCE 5.2.0. I’m still experiencing “JIT process stopped responding.”
The relevant SDKs all seem to be in the correct folders (C:/Program Files (x86)/Windows Kits/…), but the live build engine crashes with all of the Windows 10 target platforms, and it can’t find some headers if I use the 8.1 platform. I can “force” the 8.1 platform to find the correct headers by adding the system header paths manually, but then I experience the same “JIT process stopped responding!” error as before. I’ve again tried to create exporters for VS2017, VS2015 and Code::Blocks. No joy at all with this. I have absolutely no problem compiling with Visual Studio, Qt and even RackAFX projects. I’m not sure if Microsoft changed the header locations in the latest MSVC update, or whether the header content has been changed, but it seems to me like JUCE is having some issue with them.
If I go to C:/Users/UserName/AppData/Roaming/com.juce.projucer all of the log files have the following: *** Child process crashed. And as I said in my last post, Task Manager flies upto 100% CPU just before the JIT engine decides to give up. I’m on a fairly fast machine, i74930 hex core with hyperthreading, overclocked with 16GB RAM, so I wouldn’t have thought that was an issue.
Any help would be very welcome right now, I’m itching to get this thing up and running.
Unfortunately I’m also being bit by this. VS2017 with 10.0.16299.0. Happens with 5.2.1 as well as Projucer compiled from the develop branch (checked out today). I’ve forced redownloading of the compile engine and ended up with JUCECompileEngine 18.104.22.168 (md5sum is 0594b094f319bccd3ea91f11aa978893) but I’m still experiencing exactly the behaviour described here. (i.e. “Initialising JIT engine” each time a build is triggered until eventually it just says “JIT process stopped responding”)