Crash on write?

[Pacocreative]

Hey,
6.1.21 crashes when I try to write one of the modular loopers to file.
It happens every time after the popup to enter the filename.
It has write access to the drive, bc it writes project files, macros etc…

Any ideas?

[Philippe]

Hi,
Tested with 4 loopers. No crash here.
Can send the crash report please?
Also, what is the value of $current_project_saved_loops_path$ ?
Is it on the internal HD or SSD ?
How many loopers?
Can you try with a new project?
Thanks,
Philippe

[Pacocreative]

1/ I have no crash report. Any suggestions on how to create it?
2/ The same happens with previous LL – v6.0
3/ I initially tested with 4 loopers.
4/ I started a new project, one looper on insert, crashes right away.
5/ It’s an internal SSD.
6/ Paths:

$current_project$		                string	RecTest
$current_project_impulses_path$		        string	/Volumes/Data/Music/LL Projects/RecTest/Impulses/
$current_project_medias_path$		        string	/Volumes/Data/Music/LL Projects/RecTest/Medias/
$current_project_output_recorder_path$		string	/Volumes/Data/Music/LL Projects/RecTest/Output Recordings/
$current_project_path$		                string	/Volumes/Data/Music/LL Projects/RecTest/
$current_project_saved_loops_path$		string	/Volumes/Data/Music/LL Projects/RecTest/Saved Loops/

Btw, I have no problems writing using “copy to files” from an old track looper.

[Pacocreative]

From the crash reporter, I’m getting the following.
Copied only the beginning, full file here:
https://www.dropbox.com/scl/fi/d6dvbpupxa2p103g50d6s/Crash.txt?rlkey=o7gqn1k0max9kbv17liqzs9l9&dl=0

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               Logelloop 6 [70867]
Path:                  /Applications/Audio/*/Logelloop 6.app/Contents/MacOS/Logelloop 6
Identifier:            com.logelloop.logelloop6
Version:               6.1.21 (6.1.21.2526065)
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
User ID:               502

Date/Time:             2024-12-26 11:35:08.8219 +0100
OS Version:            macOS 13.6.4 (22G513)
Report Version:        12
Anonymous UUID:        852B539F-953F-9928-5AF4-2B1A87406498

Sleep/Wake UUID:       A1ECC548-ADF6-49C0-BC04-8138D18D5A93

Time Awake Since Boot: 770000 seconds
Time Since Wake:       1550 seconds

System Integrity Protection: enabled

Crashed Thread:        58  Java: Simple Buffer disk writter consumer

Exception Type:        EXC_BAD_ACCESS (SIGABRT)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes:       0x0000000000000001, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process:   Logelloop 6 [70867]

VM Region Info: 0 is not in any region.  Bytes before following region: 4379467776
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->  
      __TEXT                      105096000-107b1a000    [ 42.5M] r-x/r-x SM=COW  ...S/Logelloop 6

Application Specific Information:
abort() called

[Philippe]

Hi,
Thank you for the crash report.
We will look at it carefully but at the first look, I do not see something clear but we know which part of the code is crashing.

Could you please make some other tests ?

—> are the writing rights on the “saved loop” folder and the project folder correctly set in order that Logelloop can write in the folder ?
—> what happens if you use “WriteAudioFile” in the yellow arrow in one Looper ?
—> can you write loops using CopyToFile with the main looper ?

Thanks,
Philippe

[Pacocreative]

Write rights for the entire folder and all subfolders with projects are RW for admin and RW for users (“staff”)
LL does not have issues writing, as it successfully create project structure and own files.

“CopyToFile” works fine in the main looper, as I reported.
“Write Audio File” under yellow arrow is exactly the one crashing for me. Every time.

[Philippe]

Hi,
I had misread the paths which indicate that the project is not on the same volume as Logelloop.
And I had asked the wrong question, it can indeed be an internal SSD while being another volume! -)

So, I can reproduce the crash which happens if the project is not on the same Volume as Logelloop.
We’ll fix this soon and release a new version, but in the meantime, you can work with projects that are on the main volume.
Thanks for reporting the issue.
Philippe

[Pacocreative]

Thanks for looking into it.
Yes, it’s internal SSD, different volume.
Take your time.
My life does not depend on it.
yet.

[Author]

Posts