VM Region Info: 0 is not in any region. Bytes before following region: 4416081920
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
—>
__TEXT 107381000-108ccd000 [ 25.3M] r-x/r-x SM=COW /Applications/Studio One 7.app/Contents/MacOS/Studio One
Kernel Triage:
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
Hi @Daren welcome to the forum. Strange to hear this is happening when running both Scaler 3 as a plugin and standalone. Not that it should be happening in either.
There is an issue we are aware of regarding the template presets. Loading one of these presets then playing main track chords can in some cases lead to crashes. These presets will be updated soon to resolve this.
Would you mind please confirming if this crash occurs even when using Scaler 3 from a blank session, rather than a preset? And also have you updated Scaler 3 to v1.0.7?
Hi @Daren very odd that this is happening standalone as well. Most standalone crashes can be resolved by deleting the standalone state file: /Users/[NAME]/Library/Application Support/Scaler 3.settings
Could you please try deleting this file, then running Scaler 3 standalone and seeing if crashing persists? If so it would be very interesting to hear exactly what leads to a crash. You say this happens when selecting main track chords. Does this mean after strarting from a bank session, you drag chords down to the main track, then Scaler 3 crashes whenever you click on any of them?
Regardless this does sound very unusual so it may be worth attempting a clean re-install via the instructions on the Known Issues forum page:
Instructions for a clean Install:
Mac - Clean Install:
Delete the standalone state file in this folder: /Users/[NAME]/Library/Application Support/Scaler 3.settings
Delete the personalised files in this folder: /Users/[NAME]/Library/Scaler Music/Scaler 3
Delete the shared user files in this folder: /Users/Shared/Scaler Music/Scaler 3
Reinstall.
Tip: The Library folder is hidden by default. To access it, open Finder, click Go in the menu bar, and hold the Option (⌥) key to reveal Library.
Hi @Daren I’ve moved your other posts into this thread as they are likely related.
Scaler 3 is crashing Studio One 7 on startup
Scaler 3 standalone will no longer open (MacOS) - reboot doesn’t work
My suggestions above do apply to both these scenarios so please try first deleting the standalone state file, and if crashes persist please attempt a clean re-install:
Clicking the chords individually is fine - it’s when an attempt is made to select them all by dragging from the top left corner.
Deleting Scaler 3.settings worked - I can now open standalone and can select all chords without a crash (even after changing the default ‘Felt Piano’ to Arturia VST. However, when I load my previous saved state (attached), the crash is back. This has 3 tracks (Main, Melody and Bass); I’ve only tested a fresh session with only a Main Track (no crash).
Hi, I was demoing Scaler 3 and this happens all the time to me as well in any custom project any time I left-click and hold to select one or more chords (starting from the space after last one) in the Main Track on the arrange page.
Here’s the console report after a crash:
VM Region Info: 0 is not in any region. Bytes before following region: 4300783616
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
—>
__TEXT 10058c000-101864000 [ 18.8M] r-x/r-x SM=COW /Applications/Scaler 3.app/Contents/MacOS/Scaler 3
The original posters issue sounds exactly like my reported issue. Crashes both in standalone and as a plug in Logic (instrument and midi).
Also on macOS X86_64 here.
I have updated to 1.0.7 and still same problems. I have reinstalled a couple of times and have also pointed out that you should inform in your instruction that if you delete one of the paths in the users Library folder you will also delete your Scaler saved projects
Currently almost impossible to use Scaler for me. The computer is clean and only used for music. Scaler 2 never ever crashed and 3 have crashed it since day 1. Even corrupted Logic sessions when crashing.
I have reported this and sent all the crash logs I have to Scaler.
I can also repeatedly trigger this crash in both Ableton and Reaper. I’ve loaded a chord progression user preset that I created, tried to select all chords on the main track in Arrangement mode in order to duplicate them all. What’s also weird is that I’ve already done this once, duplicating from four bars to eight bars of the same progession. The duplication of four bars worked fine, the duplication of eight bars consistenly crashes. Scaler Main track plus 3 more performance tracks are routed to midi channel 1 in Reaper. (As an instrument on a track)
In Ableton, Scaler 3 is loaded into a M4L Midi Send Wrapper
Upon further exploration, in my crashing version, the DAW would crash when I selected the chord that had no performance pattern on the arrangement track. i.e. the Arpeggio track had no midi pattern in it.
When I add a pattern to this track, I’m able to select all the chords as normal. No crash occurs.