10-05-2018, 08:05 AM | #1 |
Human being with feelings
Join Date: Mar 2008
Location: Planet Earth
Posts: 9,055
|
Is there a log file to trace crashes?
So I'm working on the most complex song I've done in Linux, and now towards the end I'm crashing a lot. I suspect it is some effect, and have tried disabling some that I suspected, but it just did it again for about the twentieth time, and I have to reboot every time because REAPER won't complete the initialization the next time after a crash.
Anyway, I'm going to reboot now and see if I can make the final little changes to the mix before I'm done with this one. |
10-05-2018, 08:46 AM | #2 |
Human being with feelings
Join Date: May 2015
Location: Québec, Canada
Posts: 4,937
|
Running REAPER like this will give you a stack trace (gdb is the GNU debugger):
Code:
gdb reaper -ex run -ex bt
__________________
💖 Donate (PayPal) | Sponsor (GitHub) | The Endless Journey (Keyboard Ensemble) ReaPack, a package manager for REAPER | SWS 2.14 is now available in ReaPack [new!] Developer tools: Lua profiler | Interactive ReaScript | ReaPack Editor | ReaImGui Last edited by cfillion; 10-05-2018 at 09:00 AM. |
10-05-2018, 10:10 AM | #3 | |
Human being with feelings
Join Date: Mar 2008
Location: Planet Earth
Posts: 9,055
|
Quote:
Funny thing is, launching REAPER with the debug command seems to be making it crash proof now, which makes me think some timing thing might be coming into play. I hammered on the song while running it in debug mode and never got a blink, but more than twenty times today while making final edits it vaporized on me. This project is way over the top for me, and has five instances of Guitar Rig on four guitars plus a bass. Normally I would use a real amp and mic, but this was intentionally sort of a stress test project. There have been recent threads that won't die about guitar sims vs. real, and while I almost always use real, I decided to see how restricted I would be if I had to use all amp sims, and play EZ-Drummer from my midi keyboard. I finally did get this thing mixed. https://www.soundclick.com/html5/v4/...ongID=13790607 - Last edited by Glennbo; 10-05-2018 at 11:24 AM. |
|
10-05-2018, 03:59 PM | #4 |
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 15,721
|
If you run this before running REAPER:
Code:
ulimit -c unlimited Code:
gdb path/to/the/binary path/to/the/core |
10-05-2018, 04:55 PM | #5 | |
Human being with feelings
Join Date: Mar 2008
Location: Planet Earth
Posts: 9,055
|
Quote:
Starting REAPER up with "gdb reaper -ex run -ex bt" command that cfillion suggested, I finally got it to blow, although running with that command, REAPER did not close, but instead became unresponsive with pages of this message scrolling in the terminal window. JackAudioDriver::ProcessGraphAsyncMaster: Process error JackEngine::XRun: client = REAPER was not finished, state = Triggered So I terminated REAPER from the task manager and this final stuff displayed. 0046:fixme:x11drv:X11DRV_DestroyNotify window 0x20266/9600001 destroyed from the outside JackEngine::XRun: client = REAPER was not finished, state = Triggered JackAudioDriver::ProcessGraphAsyncMaster: Process error JackEngine::XRun: client = REAPER was not finished, state = Triggered JackAudioDriver::ProcessGraphAsyncMaster: Process error JackEngine::XRun: client = REAPER was not finished, state = Triggered JackAudioDriver::ProcessGraphAsyncMaster: Process error 003c:fixme:x11drv:X11DRV_DestroyNotify window 0x20262/9400001 destroyed from the outside JackEngine::XRun: client = REAPER was not finished, state = Triggered JackAudioDriver::ProcessGraphAsyncMaster: Process error JackEngine::XRun: client = REAPER was not finished, state = Triggered JackAudioDriver::ProcessGraphAsyncMaster: Process error JackEngine::XRun: client = REAPER was not finished, state = Triggered JackAudioDriver::ProcessGraphAsyncMaster: Process error Cannot write socket fd = 15 err = Connection reset by peer CheckRes error Could not write notification ClientNotify fails name = REAPER notification = 3 val1 = 0 val2 = 0 Cannot write socket fd = 15 err = Broken pipe CheckRes error Could not write notification ClientNotify fails name = REAPER notification = 3 val1 = 0 val2 = 0 Cannot write socket fd = 15 err = Broken pipe CheckRes error Could not write notification ClientNotify fails name = REAPER notification = 3 val1 = 0 val2 = 0 Cannot write socket fd = 15 err = Broken pipe CheckRes error Could not write notification ClientNotify fails name = REAPER notification = 3 val1 = 0 val2 = 0 JackEngine::XRun: client = REAPER was not finished, state = Triggered JackAudioDriver::ProcessGraphAsyncMaster: Process error Unknown request 4294967295 CheckSize error size = 0 Size() = 12 CheckRead error RemoteVSTServer::terminate: setting exiting flagRemoteVSTServer::terminate: setting exiting flag 0057:fixme:win:UnregisterDeviceNotification (handle=0xcafeaffe), STUB! |
|
10-05-2018, 05:22 PM | #6 | |
Human being with feelings
Join Date: Mar 2008
Location: Planet Earth
Posts: 9,055
|
Quote:
ulimit -c unlimited Then I started REAPER up from my icon as usual, did some editing for about five or ten minutes and it vaporized. I know the path to the REAPER binary, but I have no idea where a dump file might have been written. |
|
10-05-2018, 06:32 PM | #7 | |
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 15,721
|
Quote:
|
|
10-05-2018, 07:02 PM | #8 | |
Human being with feelings
Join Date: Mar 2008
Location: Planet Earth
Posts: 9,055
|
Quote:
JackAudioDriver::ProcessGraphAsyncMaster: Process error JackEngine::XRun: client = REAPER was not finished, state = Triggered I don't think whatever process it is that writes a crash dump is getting a chance to do anything, because there is never the slightest pause between the last action I perform and the instantaneous vaporization of REAPER. If I'm wrong about that, I still don't know where to look for a crash dump. Doesn't seem to be one in the REAPER folder with the executable, nor in my home folder. |
|
10-06-2018, 05:54 AM | #9 | |
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 15,721
|
Quote:
|
|
10-06-2018, 04:49 PM | #10 | |
Human being with feelings
Join Date: Mar 2008
Location: Planet Earth
Posts: 9,055
|
Quote:
-- kern.log -- Oct 6 13:42:45 DAW-Linux kernel: [14646.441374] show_signal_msg: 13 callbacks suppressed Oct 6 13:42:45 DAW-Linux kernel: [14646.441377] IRCalculation[6151]: segfault at 10 ip 00007feac7573696 sp 00007fea6dbf9ca8 error 6 in libc-2.27.so[7feac74b8000+1e7000] This particular project was using more instances of Guitar Rig than I've ever used in any project in Windows, as I would normally use my real guitar amp and mic it. I have more than 25 instances of LinVST running, with five of them hosting Guitar Rig and one hosting Konatakt, plus Jack is set for 128 samples, so I'm really surprised that it works at all. The only reason for my post was that I thought REAPER opened a log by default that would maybe point me to a plugin that I could temporarily disable while editing, and re-enable for rendering. The symptom seems to be that I can play the song all day long, and nothing happens, but if I start editing either midi events in piano roll, or chop audio clips up and move them around, when I hit play REAPER will close the absolute second I hit play after performing some kind of edit. It was not happening until I had finished all the recording, and was adding more and more FX for mixing, and then it got where ten or so minutes of making edits would vaporize. |
|
10-06-2018, 06:04 PM | #11 |
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 15,721
|
Try gzip or xz'ing the core file, it might be small enough to put on dropbox or google drive or something... definitely don't post it publicly though, send support at cockos dot com a link.
|
10-06-2018, 06:49 PM | #12 |
Human being with feelings
Join Date: Mar 2008
Location: Planet Earth
Posts: 9,055
|
It gzipped down to 27.7MB. Can I send that direct to support at cockos dot com? I've never setup any online storage anywhere.
|
10-07-2018, 05:18 AM | #13 | |
Administrator
Join Date: Jan 2005
Location: NYC
Posts: 15,721
|
Quote:
|
|
Thread Tools | |
Display Modes | |
|
|