Trying to open files in (unhardened)REAPER v6.08, on a late 2015 (Retina 5k, 27-inch) iMac, running OSX Mojave 10.14.6, results in near-constant crashes upon opening certain files.
Often the crashes are tied to specific plugins, but not always. Sometimes the crash can be averted by loading the plugin on an empty track in a new file FIRST, and then opening the file I'm trying to load. This "preload" of the plugin will sometimes avert the crash, although not always.
I have decided to make various "running tally" threads, here, on reaper.fm's forums, and in the Tokyo Dawn Labs sub-forums(the other plugin company whose plugins lead to problems for whatever reason)
A log of all the times reaper crashes on opening a file (when a u-he plugin is involved)
-
- KVRian
- 874 posts since 28 Nov, 2016
-
- KVRian
- Topic Starter
- 874 posts since 28 Nov, 2016
Crash #2: "dear heart.rpp"
If I make an empty track and add SlickEQ GE to the track, and then open the file, it no longer crashes on trying to load SlickEQ GE (Crash #1), instead, it crashes on trying to load Satin.
If I make an empty track and add SlickEQ GE to the track, and then open the file, it no longer crashes on trying to load SlickEQ GE (Crash #1), instead, it crashes on trying to load Satin.
Code: Select all
Process: REAPER [17420]
Path: /Applications/REAPER64.app/Contents/MacOS/REAPER
Identifier: REAPER
Version: 6.80.0 (6.80.0)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: REAPER [17420]
User ID: 501
Date/Time: 2020-04-09 13:43:54.757 -0400
OS Version: Mac OS X 10.14.6 (18G4032)
Report Version: 12
Anonymous UUID: A96C4589-AD13-01A2-00F2-28D85E35ED18
Time Awake Since Boot: 11000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 reaper Dispatch queue: com.apple.main-thread
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Trace/BPT trap: 5
Termination Reason: Namespace SIGNAL, Code 0x5
Terminating Process: exc handler [17420]
Application Specific Information:
/Library/Audio/Plug-Ins/VST3/Satin.vst3/Contents/MacOS/Satin
Thread 0 Crashed:: reaper Dispatch queue: com.apple.main-thread
0 com.u-he.Satin.vst3 0x0000000147986df9 0x147896000 + 986617
1 dyld 0x0000000115c62592 ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 506
2 dyld 0x0000000115c62798 ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 40
3 dyld 0x0000000115c5dbea ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, char const*, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 362
4 dyld 0x0000000115c5cd73 ImageLoader::processInitializers(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 133
5 dyld 0x0000000115c5ce05 ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 73
6 dyld 0x0000000115c4fcb2 dyld::runInitializers(ImageLoader*) + 82
7 dyld 0x0000000115c593dc dlopen_internal + 607
8 libdyld.dylib 0x00007fff6838dd43 dlopen + 200
9 com.apple.CoreFoundation 0x00007fff3c4644b6 _CFBundleDlfcnLoadBundle + 144
10 com.apple.CoreFoundation 0x00007fff3c503b3a _CFBundleLoadExecutableAndReturnError + 518
11 com.cockos.reaper 0x000000010655ea9b LoadLibrary(char const*) + 155
12 com.cockos.reaper 0x000000010638f17d LoadPluginFromFile(char const*, AEffect**, VST3Data**, int, bool) + 77
13 com.cockos.reaper 0x000000010638d9bd VST_HostedPlugin::OpenFromUID(char const*, int, char const*, WDL_FastString*, bool) + 4957
14 com.cockos.reaper 0x00000001063bfcfb FxDsp::LoadState(char const*, ProjectStateContext*, bool, bool) + 3179
15 com.cockos.reaper 0x00000001063d223e FxChain::LoadState_internal(ProjectStateContext*, bool, int, bool) + 1198
16 com.cockos.reaper 0x00000001063d6ec5 FxChain::LoadState(char const*, ProjectStateContext*, int, bool) + 101
17 com.cockos.reaper 0x000000010612bb14 do_load(ReaProject*, ProjectStateContext*, int) + 19156
18 com.cockos.reaper 0x0000000106134723 LoadProjectFromContext(ReaProject*, ProjectStateContext*, char const*, int) + 659
19 com.cockos.reaper 0x0000000106133ac1 LoadProject(ReaProject*, char const*, int*, int) + 817
20 com.cockos.reaper 0x00000001060aa0be DoProjectLoad(char const*, bool, int) + 1230
21 com.cockos.reaper 0x00000001060a7c95 Main_openProject(char const*) + 1061
22 com.cockos.reaper 0x0000000106061224 Main_OnCommandEx2(int, int, ReaProject*) + 76644
23 com.cockos.reaper 0x00000001060ac17d Main_OnCommandEx(int, int, ReaProject*) + 29
24 com.cockos.reaper 0x00000001063510db KBD_OnMainActionEx(int, int, int, int, HWND__*, ReaProject*) + 155
25 com.cockos.reaper 0x00000001066961d2 MainProc(HWND__*, unsigned int, unsigned long, long) + 6274
26 ??? 0x0000000000000111 0 + 273
You do not have the required permissions to view the files attached to this post.
-
tasmaniandevil tasmaniandevil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=62450
- KVRAF
- 2171 posts since 22 Mar, 2005 from a planet called u-he
Thanks for notifying us about this, and sorry for the inconvenience.
In such cases, opening a support ticket via https://u-he.com/support/ would be much more helpful, as we can react way faster over our support system.
You are experiencing a rare problem, which can lead to a crash when reopening an existing project.
Finding the cause and fixing the problem isn't easy since it's happening so rarely that we could never reproduce it on our test systems.
Even sending the problematic project will not help, as it will usually only crash on the user's computer.
We have been working on fixing this over the past months, and our recently updated products should already be free of this bug.
But since Satin wasn't among the plugins receiving a recent update, the problem can still happen with this and some other plugins.
As you already figured out yourself, the workaround is to first load an instance of Satin into an empty project, before loading the problematic project.
I cannot say when the next update for Satin is due, but be assured that it will include a fix for the problem.
In such cases, opening a support ticket via https://u-he.com/support/ would be much more helpful, as we can react way faster over our support system.
You are experiencing a rare problem, which can lead to a crash when reopening an existing project.
Finding the cause and fixing the problem isn't easy since it's happening so rarely that we could never reproduce it on our test systems.
Even sending the problematic project will not help, as it will usually only crash on the user's computer.
We have been working on fixing this over the past months, and our recently updated products should already be free of this bug.
But since Satin wasn't among the plugins receiving a recent update, the problem can still happen with this and some other plugins.
As you already figured out yourself, the workaround is to first load an instance of Satin into an empty project, before loading the problematic project.
I cannot say when the next update for Satin is due, but be assured that it will include a fix for the problem.
That QA guy from planet u-he.
-
- KVRian
- Topic Starter
- 874 posts since 28 Nov, 2016
It's been happening a lot of times, with different things, honestly—not just u-he stuff—I thought maybe it'd be better if I put the bugs in a thread, which I could update each time, instead of submitting 20 individual tickets. If you'd definitely prefer me to submit support tickets, though, I can. (unless you're implying that I don't need to post any of the other crash reports)
-
- KVRAF
- 4805 posts since 21 Jan, 2008 from oO
maybe it helps if you put a debug crashlog file on your desktop like explained here: https://u-he.com/support/faq.html#troub ... g:crashlog
And send it directly to support then. Good luck!
And send it directly to support then. Good luck!
JamWide - a cross-platform Ninjam client for DAWs
-
tasmaniandevil tasmaniandevil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=62450
- KVRAF
- 2171 posts since 22 Mar, 2005 from a planet called u-he
I checked your crash report, and it's exactly the problem I explained above. We are aware of it, and we are working on it. There is no need to post multiple crash reports of the same problem, unless it happens with different u-he plugins. In this case sending one crash report for every plugin with which you experience this is a good idea.
Usually, when a user gets the problem, it's one specific project file which is causing it. This will, of course, crash pretty much every time you try to load it, unless you use the described workaround.
Usually, when a user gets the problem, it's one specific project file which is causing it. This will, of course, crash pretty much every time you try to load it, unless you use the described workaround.
That QA guy from planet u-he.
-
tasmaniandevil tasmaniandevil https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=62450
- KVRAF
- 2171 posts since 22 Mar, 2005 from a planet called u-he
While it's usually a good idea to get a log file, in this specific case it's not needed, as the log does not contain any useful info about the problem.irre wrote: Thu Apr 09, 2020 7:41 pm maybe it helps if you put a debug crashlog file on your desktop like explained here: https://u-he.com/support/faq.html#troub ... g:crashlog
That QA guy from planet u-he.
-
- KVRian
- Topic Starter
- 874 posts since 28 Nov, 2016
Alright. Thank you for your prompt replies and stuff.