Debug in VS2022

[d.healey]

@DanH Is it an error? Is there a breakpoint there?

[DanH]

@d-healey Here's what it looks like. What should breakpoints look like?!

[d.healey]

@DanH Ah ok, that's a jassert. So now you have to figure out why that case of the switch statement is being reached.

To the call stack with you! (also check the console) :)

[Lindon]

@DanH -- in your jassert its falling thru to the default option- so are you sure you have the direction control set up in your arp?

[DanH]

@Lindon @d-healey yep so I found the direction knob in my project which wasn't being used, deleted any code to do with it and recompiled. I'm still running into the same issue.

Lindon do you mean I need to have something set up for the direction? I've opted out of using it.

From the console:

JUCE Assertion failure in Arpeggiator.cpp:810
A breakpoint instruction (__debugbreak() statement or a similar call) was executed in HALO-2 Debug.exe.

[Lindon]

@DanH well yes - generally you'd need to tell the arp which direction to go in...

[DanH]

@Lindon sure but it has a default setting... oooor does it.....

Ok so in my project they were all unspecified... i.e no direction set. Bravo!

Will recompile and try again!

[DanH]

@Lindon ok we got past that one! Cheers for the help :)

Onto the next one! Please let me know if you have any ideas, I can't see a 'Gain Mode' on any envelopes...

[Lindon]

@DanH "Show Call Stack"

[DanH]

@Lindon thanks, I found the culprit and now have an open app in VS :thumbs_up:

[Lindon]

@DanH said in Debug in VS2022:

@Lindon thanks, I found the culprit and now have an open app in VS :thumbs_up:

yes - so now the fun begins....

[DanH]

@Lindon indeed! So when playing notes on my instrument the console spits out messages like the below - anything to worry about?!

The thread 0x206c has exited with code 0 (0x0).
The thread 0x20f4 has exited with code 0 (0x0).
The thread 0xbdc has exited with code 0 (0x0).
The thread 0x468 has exited with code 0 (0x0).

[DanH]

@Lindon @d-healey @Christoph-Hart

Ok I'm pretty sure the below is the bug I'm trying to locate. It happens very occasionally when switching presets via the usual browser (can be any preset). I have no idea what this is telling me so please let me know if you do! :)

The instrument contains a couple of samplers, Waveform Gens, Sine Wav Gen too....

### Loading user preset BA        2010

Assertion failed!

Program: D:\HALO-2\Binaries\Compiled\App\HALO-2 Debug.exe
File: C:\Users\Admin\Desktop\HISE-develop...\readerw...queue.h
Line: 566

Expression: !inSection && "ReaderWriterQueue does not support enqueuing or dequeuing elements from other elements' ctors and dtors"

[d.healey]

@DanH Why are you taking photos of your screen instead of screenshots?

[DanH]

@d-healey it's not my main machine and the internet is dodgy on there at the mo

[d.healey]

@DanH Ok, just checking your sanity, I thought the debugging might have got to you :D

[DanH]

@d-healey I suspect it will, given time!

Screenshot below!

[DanH]

@DanH so a quick google suggests this might have to do with the queuing and de-queuing of threads. What kind of threads should I have going on normally...?

[Christoph Hart]

That‘s just an assertion that is telling you that the UI notification queue is full (which might happen if the user preset restores multiple hundred controls). It‘s not an critical error though so if it keeps appearing, just remove that line and rebuild to silence the message.

[DanH]

@Christoph-Hart Ok thank you for looking! This is what came up with the crash and the call stack is the same as when the plugin crashes (in the error report).... Could this lead to the source of the crash?