3.0.15 Crashing on MacOS

[pixpop]

I'm experiencing a lot of crashes on Macos.

Details:
Macos version 10.13.6
TX16Wx version 3.0.15 5102.1324



To make this happen, I drop a .wav file into the main blank area, immediately after opening the plugin. The auto mapping dialog comes up. I click OK, and then it crashes. Sometimes it will get past this point, but then crash when I play a few notes. I've reproduced this in Bidule, Reaper, and Garage Band.



Crash report:

Date/Time: 2018-12-26 08:38:55.107 -0800
OS Version: Mac OS X 10.13.6 (17G4015)
Report Version: 12
Anonymous UUID: 9D132CF1-6D06-3B8F-4327-8ACF3DCDE295


Time Awake Since Boot: 1000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.CoreFoundation 0x00007fff444a4470 __CFRunLoopDoObservers + 352
1 com.apple.CoreFoundation 0x00007fff44486801 CFRunLoopRunSpecific + 385
2 com.apple.HIToolbox 0x00007fff43766d96 RunCurrentEventLoopInMode + 286
3 com.apple.HIToolbox 0x00007fff43766a0f ReceiveNextEventCommon + 366
4 com.apple.HIToolbox 0x00007fff43766884 _BlockUntilNextEventMatchingListInModeWithFilter + 64
5 com.apple.AppKit 0x00007fff41a16a73 _DPSNextEvent + 2085
6 com.apple.AppKit 0x00007fff421ace34 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044
7 com.apple.AppKit 0x00007fff41a0b885 -[NSApplication run] + 764
8 com.plogue.bidule 0x0000000100843694 0x100000000 + 8664724
9 com.plogue.bidule 0x00000001008607cf 0x100000000 + 8783823
10 com.plogue.bidule 0x00000001006286b8 0x100000000 + 6457016
11 com.plogue.bidule 0x0000000100823b41 0x100000000 + 8534849
12 com.plogue.bidule 0x00000001006e98ce 0x100000000 + 7248078
13 com.plogue.bidule 0x00000001000b4614 0x100000000 + 738836
14 com.plogue.bidule 0x0000000100052d48 0x100000000 + 339272

[pixpop]

I was able to downgrade to version 2.4.2h, and found that the crash does not occur in that version. In that version, the auto-mapping dialog does not appear.

I was also able to verify that I can load a .wav by using the file->open button in the Wave editor. The crash only happens when I drag a sample from either the file browser or from the OS file manager onto the TX16Wx panel. I have a hunch that it's related to the auto-mapping dialog, rather than to the sample that's being loaded.

I also verified that the crash happens the same in either the AU, VST, or VST3 versions of the plugin.

[pixpop]

Further testing: I found an older version 3 on my backup disk, and found that the crash doesn't happen with that version.

That version is: TX16Wx 3.0.5 5045.1393

So this looks like a regression introduced since 3.0.5. I don't have any other versions I can test to narrow it down.

[elcallio]

Regressions we do not like. However, I fail utterly at reproducing this on OSX 10.13 (or .14). The partial crash report above does not even crash in TX16Wx per sé, which makes it even harder to figure out what is wrong. Do you have other, complete crash logs?

You can turn of automatically opening the token based auto mapper in the region editor toolbar (the piano key icon button).

[pixpop]

Hopefully you can see one at the link below.

Please note, I just now tested it with Bidule in 32 bit mode, and did not reproduce the problem. Only seems to happen in 64 bit mode. Historically, I've found other plugins that work better with Bidule in 32 bit mode.

I'll see if I can also extract a crash from Reaper or Garage Band.

https://www.dropbox.com/s/uysi7ararqtm1 ... h.txt?dl=0

[pixpop]

Do you have any older versions between 3.0.5 and 3.0.15 that I can try?

[elcallio]

Still cannot repro this. Running Bidule on 10.13.6 crashes quite a bit for me, but that might just be due to running it in a VM (i.e. borked ogl graphics) - it crashes on window resize etc, long before loading TX. Cannot make it misbehave with anything in TX though.
You said you get crashes in reaper also, do you have a dump file from it?

[pixpop]

Well, I don't know what I did, but I can no longer reproduce it in Reaper or Garage band. I can still reproduce it in Bidule, but as I mentioned above, only when I run Bidule in 64 bit mode. I'll keep poking at it on those other hosts to see if I can get another crash report, and will post it here if so.

[Sylenthia]

I would like to join in with a different yet similar problem:

MacOS Catalina / GarageBand
So far I was using TX16W 2.4.2g but thought it might be a good idea to upgrade to the newest v3. So I did that and...well I wanna downgrade since half of my projects aren't working with that upgrade. I get errors, samples are missing/mute or sound different than they should. I am not in the mood to change all this so I really would like to just downgrade back to 2.4.2h. So I downloaded it from the legacy page and run the installation. But when I open it, it still is v3.3.0. Also the .component files in Finder says 3.3.0. How can I properly downgrade to the old state?

Thanks!

EDIT: Meanwhile I tried to delete the .component and .VST files before installing 2.4.2h. At first I thought that helped but now GB crashes on startup for some projects. Still unsolvable. Please help.

[elcallio]

If you resaved projects using v3, they will not open on v2.
As for downgrading on OSX: make sure to manually remove all files and settings before installing, and reboot/log out+in to reset the AU caches.
OSX is not installer friendly.

[Sylenthia]

Thanks. Do you have a list of all files and folders that I need to delete? There is more than just the .component / .vst files. So I delete them all, reboot my Mac, install v2, reboot my Mac and then it should work, right?

[elcallio]

Honestly, since it is a Mac, I will make no guarantees whatsoever. But make sure to remove anything in
/Library/Application Support/TX16Wx
and
~/Library/Application Support/TX16Wx
and it _should_ behave as pristine. But then again, OSX...

Also, you could opt to simply send the projects + samples that don't load correctly and I can maybe try to fix whatever incompatibility you are seeing. Since v2 will not be updated or bugfixed.

[Sylenthia]

Thanks, I will give it a try. I would just like to use the v2 vor GB and may get used to v3 when working with Logic since Logic was not able to open v2. But I guess a plugin can only work as one version and not as 2, like v2 for GB and v3 for Logic. So first important is that I can finish all my GB projects with v2 and then maybe in the future when I am completely into Logic then I might consider upgrading to v3 and get used to that as well to use it in Logic. So, I will reply back.

[Sylenthia]

So it didn't work. Deleted all files, folders, reboot mac, installed v2, reboot mac. Upon loading projects an error occurs and crashes GB. So I can't even start it.

Guess I will have to get used to v3. So I re-installed v3 and am about to set Settings. What settings are best to prevent incomatibility between DAW & projects? Save all waves in FXB & projects? Using the Banks etc. system? So far I only saved everything within my projects with just the GB saveing. I admit having quite a few problems understanding the user manual. My english is not that bad but...is there a more enhanced explanation on all the settings?

[elcallio]

Unless you need to move your projects or switch computers, I would keep "save waves in fxb/projects" off. The latter won't do anything in garageband anyway.
Actually, settings should have no impact whatsoever on compatibility.
Saving things as banks/perfs/programs etc is for if you want to create presets and reuse between projects.