Crash - can someone confirm?

[dannytaurus]

Reproduce:

1. Start a new project
2. Click on FX in the Module tree to open the empty FX panel
3. Open the HISE Controller keyboard popup
4. Click the 4-way arrows top left (✥) to lock the popup
5. Click anything in the Module Tree (MIDI Processor, Interface, etc) = CRASH

Can anyone reproduce? If not, this is something weird on my system.

If so, I have to assume this is a known bug? If not, I'll create an issue on GitHub.

[dannytaurus]

EDIT: I should know better than to leave this stuff out

Machine: 2020 M1 MacBook Air 8GB RAM / Sonoma 14.7 / Xcode 16.0
Using develop branch and latest commit as of writing, which is passing CI.
HISE commit: fix typo a20873ea7a8c00b251ddae7df8d6e3007f8c5f71

[d.healey]

@dannytaurus said in Crash - can someone confirm?:

Click on FX in the Module tree to open the empty FX panel

Do you mean add a script fx?

[dannytaurus]

@d-healey No, just click FX in the Module Tree to open the empty FX popup.

It happens when a module popup is open, then open and lock the HISE Controller, then click anywhere in the Module Tree again.

[dannytaurus]

Video, so you can see the start and end, and pause if needed: https://imgur.com/a/Ey0JwDX

[d.healey]

@dannytaurus No crash here. Does it happen in the Release build?

[dannytaurus]

@d-healey It takes my machine an hour to build the Debug build. I can try a Release build, but probably need to leave it running overnight .

[d.healey]

@dannytaurus said in Crash - can someone confirm?:

It takes my machine an hour to build the Debug build. I can try a Release build, but probably need to leave it running overnight

That's crazy, what's the bottleneck on your system?

[Allen]

I tried this with three diiferent versions of Hise and one got crashed (961d7d9).

Here's debug result

I not sure but seems like there's a conflict occurred when the floating tile loading contents.

[ustk]

@dannytaurus @Allen Nice catch, crashing too here...

[dannytaurus]

@d-healey RAM, I think. Swap and Memory Pressure go off the charts in Activity Monitor.

My Mac is basically unusable for the whole hour that it's compiling.

[d.healey]

@dannytaurus How much RAM do you have?

Never mind, just saw your earlier post.

8GB is plenty, something else is going on. I use a VM with 8GB and 4 threads and it doesn't take too long to build.

[ustk]

@d-healey @dannytaurus Could it be related to a multi-threading not optimised for mac when using xcode? I reckon a discussion about this and a possible flag to enable/disable. I think it's about the mac preferring to work with a single thread or something like that...

[d.healey]

@ustk You can set the preferred number of threads with defaults write com.apple.Xcode PBXNumberOfParallelBuildSubtasks 8 but it should default to all threads, and since he says his computer is unusable during the build I suspect it is using all threads already.

[ustk]

@d-healey Yeah I've seen that command, but then I don't know what "still single-threaded" means if we can set the number of threads...

https://forum.hise.audio/topic/7876/do-i-need-a-m1-m2-machine-for-apple-silicon-support/6?_=1749397285786