Develop branch cannot support more than 19 scripts

d.healey

@lindon The main project I've been working on for a couple of months has 21 included scripts and is stable. I suspect it's what's in your scripts. Now that you've narrowed it down to particular scripts, start commenting the contents of the scripts out.

One thing you can do to narrow it down more quickly is run the debug build inside Visual Studio, open your project, and see if it crashes/freezes and reports some errors.

Lindon

@d-healey - well sadly yes and no.

Scripts 20 to 27 are all exactly the same...they are simple per-voice note range filters:

function onNoteOn()
{
    if (FadeButton.getValue() == 0)
    {
        // not fading out strictly cutting off
        if(Message.getNoteNumber() < LowRange.getValue() || Message.getNoteNumber() > (HighRange.getValue()))
        {
            Message.ignoreEvent(true);
        }
    }else{
        //cut things outside the fade ranges...
        if(Message.getNoteNumber() < LowRange.getValue()-12 || Message.getNoteNumber() > (HighRange.getValue()+12))
        {
            // outside everything - just cut.
	        Message.ignoreEvent(true);
        }
        if (Message.getNoteNumber() > HighRange.getValue() && Message.getNoteNumber() <= (HighRange.getValue()+12))
        {
            // in the high range fade range
            Message.setVelocity(Message.getVelocity()* SubMults[Message.getNoteNumber() - HighRange.getValue()]);
        }
        if (Message.getNoteNumber() < LowRange.getValue() && Message.getNoteNumber() >= (LowRange.getValue()-12))
        {
            // in the low range fade range
            Message.setVelocity(Message.getVelocity()* SubMults[LowRange.getValue() - Message.getNoteNumber() ]);
        }
        
    }
	    
}

I add script 20 with this code in it, and we are stable, I add script 21 with exactly the same code in it and we are not.

d.healey

@lindon Are we talking about include scripts in the main interface script or about midi processors?

Lindon

@d-healey we are talking about in the midi processors - and just to prove my point I loaded 20 scripts with code in them, then loaded 7 more with no code in them....


function onNoteOn()
{
   
}
 function onNoteOff()
{
    
	    
}
 function onController()
{
	
}
 function onTimer()
{
	
}
 function onControl(number, value)
{
	
}

20 = stable
27 = unstable....

d.healey

@lindon

we are talking about in the midi processor

Ah ok, my mistake, I thought we were talking about includes.

Here's an empty project with about 50 empty midi processor scripts, does this crash on your system?

HiseSnippet 909.3oc6b1sSaCCE.1ApQqc+HPiGfdIHwPozxOS6hwn+LUsUnZkg1cHShK0hD6pDG1pl1axdX1izdC1rSBzxnpCp1lNS5zKppO1mli8mak9t4zMR4wiiUQDmhGOZHm37HZuQR8f5CXBIocChySncXwZdT4rPGLZHKNl6SbbV701.NEKPRe88Wd.KfI83iCQHmnDd72JBE5wQ6t+aDAAsX97iEgSr5Z621SIqqBTIl5YQpKYHy6B147CY1ks.k3rTSegVE0Syz7XyZNP4Op2.0GkYq+DQr3r.tcPEROyWTVXR8Ah.+tWsWiIDmBcGuyWLamuJsivWbc7wm.KmNQ4wYL4YfyBypjpbOJopSTRExJoUn87hDC0imwVOOj1VZ.Rel4ndxRIasDmuQqqLKPp2LjcAuUjYv0Ir1NttaT1715unehzSKTxxJ4gJM+H4ZqW5ykJV5KkJ+qS0u+Tmy9XhTAA7noNsktQyJw0jIgmwi1n7krfD90Kzr8u4Y5R2syTurc8DKTIaKE5iFxyG2RE3aOqre91DfjerY9z6a2foYFn3jGyrtg7HsvVNNM3WZtUmgnhzF73Kzpgl602Q98z7niuQUYpb7qzx++vH5eJFAItrExEPxkpHW.IWpgbAjbYajKfjK6fbAjbYWjKfjK6gbAjb44HW..WV81dktHXfIXPiefBFT4GnfAc9AJXPoefBFz5GnfA09AJXPuefBFT7GnfAM+gIX1BM+AJXPyefBFz7GnfAM+AJXPyefBFz7GnfAM+AJXPyefBFz7GnfAM+gIXphl+.ELn4OPACZ9CTvfl+.ELn4OPACZ9CTvfl+.ELn4OPACZ9CTvfl+vDL0PyefBFz7GnfAM+AJXPyefBFz7GnfAM+AJXPyefBFz7GnfAM+AJXPyeXBlsQy++sfYYZGkeR.Sey9DosgXlOg4L3FLw1AFkwB8nIaXl2ilGo6Ladj20RbEZWg1avzqwElRMZNo9aTi4sbyGSa1uO2SOt.KPa8g4s+Z9ad7uSknExy6vzQhOYtucXRXOURjG27zkRdf8NnyB1aKYicsism.83R+zA+v7JexJ1wN4SV4pIIgLuH0odY27sM0yGjFwTSxzdXZQZG63xUHo+ZvjG0cSWRnvWbpmmc6+LyE3omyVyQNUmibpMG4r8bjyNyQN6NG4r2Lyw1ZWeUhVEl8yASftMS+KBGmlRl4lU5sPxOw9uR9e

Christoph Hart

function onNoteOn()

that function name is reserved for callbacks, might be a clue why it breaks?

d.healey

@christoph-hart I think he's showing the code in his callback

Lindon

@d-healey - yes he is...

Lindon

@d-healey - no it doesnt so its not the number of scripts then... I will continue to investigate...

Lindon

@lindon -- occasionaly I'm getting this:

d.healey

@lindon Try the visual studio debug, that might help narrow it down a bit

Lindon

@d-healey - LOL dont really know how to do that...Google here I come...do I build the debug version and then run it from the Debug menu in Visual studio?

Lindon

@lindon

OK well clearly I dont know what I'm doing but I ran HIS Ein teh debugger and tried to load my project and got a log (HISE didnt "crash" it just hung so huh...)

What do I do with this stuff?

'HISE Debug.exe' (Win32): Loaded 'C:\HISE\projects\standalone\Builds\VisualStudio2017\x64\Debug\App\HISE Debug.exe'. Symbols loaded.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\ntdll.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\kernel32.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Program Files\AVAST Software\Avast\aswhook.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\KernelBase.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\user32.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\win32u.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\gdi32.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\gdi32full.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\msvcp_win.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\ucrtbase.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\comdlg32.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\msvcrt.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\combase.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\rpcrt4.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\SHCore.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\shlwapi.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\shell32.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\advapi32.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.19041.1110_none_60b5254171f9507e\comctl32.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\sechost.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\ole32.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\oleaut32.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\ws2_32.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\imm32.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\wininet.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\winmm.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\version.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\dbghelp.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\opengl32.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\glu32.dll'. Cannot find or open the PDB file.
JUCE v6.1.3
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\kernel.appcore.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\bcryptprimitives.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\uxtheme.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\msctf.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\clbcatq.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\twinapi.appcore.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\DataExchange.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\d3d11.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\dcomp.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\dxgi.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\twinapi.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\OneCoreUAPCommonProxyStub.dll'. Cannot find or open the PDB file.
onecore\com\combase\dcomrem\resolver.cxx(2299)\combase.dll!00007FFF8B15206D: (caller: 00007FFF8B154F4E) ReturnHr(1) tid(558) 80040154 Class not registered
onecore\com\combase\dcomrem\resolver.cxx(2507)\combase.dll!00007FFF8B154F76: (caller: 00007FFF8B151A05) ReturnHr(2) tid(558) 80040154 Class not registered
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\windows.storage.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\wldp.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\ntmarta.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\winmmbase.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\MMDevAPI.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\devobj.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\cfgmgr32.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\wdmaud.drv'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\avrt.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\ksuser.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\AudioSes.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\powrprof.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\umpdc.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\msacm32.drv'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\msacm32.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\midimap.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\dsound.dll'. Cannot find or open the PDB file.
JUCE Assertion failure in juce_win32_asio.cpp:1519
HISE Debug.exe has triggered a breakpoint.

'HISE Debug.exe' (Win32): Loaded 'C:\Program Files\Audient\USBAudioDriver\W10_x64\audientusbaudioasio_x64.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\setupapi.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\bcrypt.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\wintrust.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\crypt32.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\msasn1.dll'. Cannot find or open the PDB file.
The thread 0x34b0 has exited with code 0 (0x0).
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\d2d1.dll'. Cannot find or open the PDB file.
The thread 0xf54 has exited with code 0 (0x0).
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\DWrite.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\d3d10warp.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\ResourcePolicyClient.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Unloaded 'C:\Windows\System32\ResourcePolicyClient.dll'
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\DriverStore\FileRepository\nvcvwu.inf_amd64_166fee8ea72cb783\nvinitx.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\DXCore.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Unloaded 'C:\Windows\System32\DriverStore\FileRepository\nvcvwu.inf_amd64_166fee8ea72cb783\nvinitx.dll'
The thread 0x17c8 has exited with code 0 (0x0).
The thread 0x374c has exited with code 0 (0x0).
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\TextInputFramework.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\CoreUIComponents.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\CoreMessaging.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\WinTypes.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\CoreMessaging.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Unloaded 'C:\Windows\System32\CoreMessaging.dll'
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\WinTypes.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Unloaded 'C:\Windows\System32\WinTypes.dll'
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\mscms.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\userenv.dll'. Cannot find or open the PDB file.
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\coloradapterclient.dll'. Cannot find or open the PDB file.
The thread 0x16e0 has exited with code 0 (0x0).
The thread 0x144 has exited with code 0 (0x0).
'HISE Debug.exe' (Win32): Loaded 'C:\Windows\System32\TextShaping.dll'. Cannot find or open the PDB file.
The thread 0x1788 has exited with code 0 (0x0).
The thread 0x2fa4 has exited with code 0 (0x0).
The thread 0xfb0 has exited with code 0 (0x0).
The thread 0x2730 has exited with code 0 (0x0).
The thread 0x349c has exited with code 0 (0x0).
The thread 0x3500 has exited with code 0 (0x0).
The thread 0x1f48 has exited with code 0 (0x0).
The thread 0x1c68 has exited with code 0 (0x0).
JUCE Assertion failure in misctoolclasses.h:191
HISE Debug.exe has triggered a breakpoint.

JUCE Assertion failure in misctoolclasses.h:191
HISE Debug.exe has triggered a breakpoint.

JUCE Assertion failure in misctoolclasses.h:191
HISE Debug.exe has triggered a breakpoint.

JUCE Assertion failure in misctoolclasses.h:191
HISE Debug.exe has triggered a breakpoint.

JUCE Assertion failure in misctoolclasses.h:191
HISE Debug.exe has triggered a breakpoint.

JUCE Assertion failure in misctoolclasses.h:191
HISE Debug.exe has triggered a breakpoint.

JUCE Assertion failure in misctoolclasses.h:191
HISE Debug.exe has triggered a breakpoint.

JUCE Assertion failure in misctoolclasses.h:191
HISE Debug.exe has triggered a breakpoint.

JUCE Assertion failure in misctoolclasses.h:191
HISE Debug.exe has triggered a breakpoint.

JUCE Assertion failure in misctoolclasses.h:191
HISE Debug.exe has triggered a breakpoint.

JUCE Assertion failure in misctoolclasses.h:191
HISE Debug.exe has triggered a breakpoint.

JUCE Assertion failure in misctoolclasses.h:191
HISE Debug.exe has triggered a breakpoint.

JUCE Assertion failure in misctoolclasses.h:191
HISE Debug.exe has triggered a breakpoint.

HEAP[HISE Debug.exe]: Invalid address specified to RtlValidateHeap( 000001F84FA80000, 000001F85B112950 )
HISE Debug.exe has triggered a breakpoint.

Debug Assertion Failed!

Program: ...andalone\Builds\VisualStudio2017\x64\Debug\App\HISE Debug.exe
File: minkernel\crts\ucrt\src\appcrt\heap\debug_heap.cpp
Line: 904

Expression: _CrtIsValidHeapPointer(block)

For information on how your program can cause an assertion
failure, see the Visual C++ documentation on asserts.

(Press Retry to debug the application)
The thread 0x608 has exited with code 0 (0x0).
The thread 0x274c has exited with code 0 (0x0).
The thread 0x9f8 has exited with code 0 (0x0).
The thread 0x2f30 has exited with code 0 (0x0).
The thread 0x938 has exited with code 0 (0x0).
The thread 0x1ca0 has exited with code 0 (0x0).
The thread 0x3010 has exited with code 0 (0x0).
The thread 0x2d68 has exited with code 0 (0x0).
The thread 0x2cd0 has exited with code 0 (0x0).
The thread 0x295c has exited with code 0 (0x0).
The thread 0x36d0 has exited with code 0 (0x0).
The thread 0x558 has exited with code 0 (0x0).
The thread 0x728 has exited with code 0 (0x0).
The thread 0x14a8 has exited with code 0 (0x0).
The program '[2092] HISE Debug.exe' has exited with code 0 (0x0).

It seems theres something wrong in misctoolclasses.h:191

d.healey

@lindon said in Develop branch cannot support more than 19 scripts:

It seems theres something wrong in misctoolclasses.h:191

I also see a mention of juce_win32_asio.cpp.

I'm not familiar with the VS debugger but you need to step through the code if possible to see what's causing the issue. If you add a breakpoint to those files and lines that are reported in your output above that might be a good place to start.

Lindon

@d-healey right well - assigned a breakpoint and here I am (what am I supposed to be looking for?)

-- we appear to be in the sample loading thread....

d.healey

@lindon Click on the call stack tab, bottom right, and you can go back through the call history to hopefully see where this issue is starting from.

Lindon

@d-healey right did that and it shows me this:

d.healey

@lindon Does clicking through that list reveal anything useful to you?

Lindon

@d-healey no.

d.healey

@lindon Then I'd go back to the commenting out lines of code technique. If you want to send the project to me I could take a look at it and see if I can spot anything.

Develop branch cannot support more than 19 scripts

23

1.8k

11.9k

104.0k