Latest Tip - New Jucer will not run on Windows


#1

In trying to solve some issues I was having on Windows with the new Jucer, I downloaded the latest tip this morning but now have an entirely nonfunctional Jucer :cry:

The latest build compiles happily, but will not run. Output is as follows:-

‘Jucer.exe’: Loaded ‘D:\User Files\David\Programming Projects\JUCE_LATEST\extras\Jucer (experimental)\Builds\VisualStudio2008\Debug\Jucer.exe’, Symbols loaded.
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\ntdll.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\kernel32.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\KernelBase.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\user32.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\gdi32.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\lpk.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\usp10.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\msvcrt.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\advapi32.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\sechost.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\rpcrt4.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\sspicli.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\cryptbase.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\comdlg32.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\shlwapi.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7600.16661_none_ebfb56996c72aefc\comctl32.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\shell32.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\ole32.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\oleaut32.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\msvfw32.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\winmm.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\wininet.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\urlmon.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\crypt32.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\msasn1.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\iertutil.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\ws2_32.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\nsi.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\version.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\imm32.dll’
‘Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\msctf.dll’
JUCE v1.53.36
’Jucer.exe’: Loaded ‘C:\Windows\SysWOW64\uxtheme.dll’
‘Jucer.exe’: Loaded 'C:\Windows\SysWOW64\dwmapi.dll’
Another instance is running - quitting…
The program ‘[1920] Jucer.exe: Native’ has exited with code 0 (0x0).

Another instance is most definately not running, this happens even after a fresh reboot. Release builds just bail instantly, presumably for the same reason.

Cheers
Dave


#2

That’s utterly bizarre - I just had the exact opposite problem.

Yesterday, when I was doing some builds, I tried the jucer on win32 and it failed to run, with exactly this problem. Doing some digging, I found that it was failing to create an InterProcessLock, and therefore assuming another instance was running, and quitting. The reason it was failing to create the lock was a complete mystery, but when I changed it from using a “global” mutex to a “local” one, it all started working, so I assumed that Win7 was simply not giving the app permission to create a global object, and committed that change. Which OS are you using? Perhaps it needs to be more specific, e.g. maybe it should use a local mutex on win7 but a global one on vista…?


#3

This is on Windows 7 x64. I have also Windows 7 x32, Vista x32 and Windows XP test machines so I can test any patch pretty thoroughly if you want.

Cheers
Dave


#4

i’m on win7 x64 too, it builds and runs fine on JUCE v1.53.37


#5

That’s not the same build…guess I should update and try again :slight_smile:


#6

that’s what i’m saying :slight_smile: jules is fast.


#7

So does the latest one work on everyone’s machines? I’ve tweaked it so that it will try to open either a local or global mutex depending on which one actually works. But I’ve no idea why your Win7 machine fails to create a local one and mine fails to use a global one…


#8

1.53.37 builds and runs here on Windows 7 x64. Haven’t tried it on any other boxes yet.

Cheers
Dave