Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER Bug Reports

Thread Tools Display Modes
Prev Previous Post   Next Post Next
Old 05-29-2009, 06:07 AM   #1
Super Moderator (no feelings)
Ollie's Avatar
Join Date: Dec 2007
Location: On or near a dike
Posts: 9,836
Default How to report bugs and crashes - read me first before posting!

How to report bugs:

Thank you for reporting a bug! Here's how you can make a bug report most helpful for us all:

What is a REAPER bug anyway?
+ Native Reaper functions misbehaving (used to work on previous version, unexpected change in behavior of that function, obvious regression)

+ Reaper crashes (without involvement of 3rd party software, crashing module is a part of Reaper. Please see below for how to retrieve crash logs!)

1. Bug report format

* Give your report a meaningful title
Use a few descriptive words for a thread title like "[6.10]Crash in WTF.DLL when moving item" or "[6.11]XY action not working" if possible.
* Provide steps to reproduce the bug
If a bug can't be reproduced, it's incredibly hard to fix it. Please write a recipe or list of steps that have to be executed in order to reproduce the bug.

Finding a recipe also helps you to examine the nature of the bug closer and detecting important circumstances to include in your report, this in turn helps the developers.

Originally Posted by Example recipe
- Create a new midi item
- Open the MIDI editor
- Insert some notes
- Select last note
- While the last note is selected, do action 'Edit: unselect all'
- Perform action 'Navigate: Select next note'
- Reaper closes itself - no save dialog
* Describe what you expect to happen and what happens instead.
A short description of what you did exactly, what you expected to happen and what really happened instead. (No novels please ). An animated GIF often says more than 1000 words - get LICEcap here.
* List your computer specs
This should always include:

- The exact OS version you are using ("XP Pro SP3" or "OSX 10.5.6")
- The REAPER version (if you didn't put that in brackets in the thread title), please state whether you use the 32 or the 64 bit version.

Hardware specs are usually not needed unless you have a blue screen crash or some performance-related regression:

- Your soundcard/interface type and model
- Your CPU type and/or exact model ("Intel 2.4GHz" = bad. "i5 2.4GHz" or "AMD Ryzen" is better.)
- Amount of RAM
* Create a little project demonstrating the bug
If you see fit, create a little project stripped down to what's needed to demonstrate and reproduce the bug. Media files are not needed in most cases, so attach the .RPP project file, or (if it's bigger or media files play a role in the bug) upload it to a file hoster and post the link.
* Please post error/crash messages!

This can't be stressed enough: Please include error messages verbatim (or make a screenshot) and include crash logs.

2. How to submit crash logs:


1) If Windows gives you crash notification window that includes text such as:
Faulting application name: reaper.exe, version X.X.X.x
Faulting module name: XYZ
Fault offset: 123456
Take a screenshot or copy all of the text available in that window to include with your post.

2) If REAPER quits to the desktop unexpectedly, then you will need to run the event viewer to see why.

To run the event viewer, go to the start menu, choose "Run", and type "eventvwr" followed by enter.

Alternatively (depending on the Windows version you are using) you can search the start menu for "event viewer", or go to Control Panel / Administrative Tools / Event Viewer.Once you are running the Event Viewer, you will need to navigate to Windows Logs->Application.

This will likely be a very large list of events, so you can search this list using Ctrl+F and enter "REAPER". The source of the event that is most helpful is "Application Error", and the level is "Error". In this there should be text such as:

Faulting application name: reaper.exe, version X.X.X.x
Faulting module name: XYZ
Fault offset: 123456
Take a screenshot or copy all of the text available in that window to include with your post.

If this doesn't work, you can also configure Windows to create a dump file if reaper.exe crashes. To do this, run the REAPER installer, go to "optional functionality", and enable "Configure Windows to save REAPER crash dumps." Reboot your computer, then run REAPER and duplicate the crash. Once the crash occurs, a dump file should be created in %LOCALAPPDATA%\CrashDumps (Start->Run, paste that path in there). If you create a dump file this way, see the next section:

3) If REAPER hangs and is not responsive, but does not outright crash, you can generate a dump file which will be helpful in determining why.

To create a dump file, while REAPER is not responding, open the task manager (Ctrl+Alt+Delete, then choose Task Manager), right click on reaper.exe, and choose "Create Dump File". The task manager should respond with a box that states the path to a file that it generated.

Once you have a dump file: you will want to .zip this file (it may be quite large), then upload it somewhere in order to share it with us.

PLEASE NOTE -- for your own privacy you should not share links to dump files publicly. Instead, upload the zipped file somewhere private (e.g. dropbox, wetransfer, etc), and email a link to support at cockos dot com, and include a copy of your bug report.


1) If macOS gives you a Problem Report window, choose "Show Details" and proceed to step 3.

[B][I]2) If the crash happened earlier and you didn't save the log, you can find them via the 'Console' app (the easiest way to do that is to use Cmd+Space to run spotlight, then type "Console.app" and enter).

Once within Console.app, select "Crash Reports", then scroll the list to find the log that corresponds to your crash.

3) Once you have the crash report (via method 1 or 2) -- if you can email an entire copy of this crash report to support at cockos dot com, that would be ideal.

If you want to include only a small section for a forum post, you should include the Version: lines, the "Crashed Thread" line (noting the thread that crashed, e.g. "X")...

...and scroll down to find the "Thread X" line, and copy the dozen or so lines following that until the next "Thread" line.

BSOD/Computer restarts itself:
If you had a Blue Screen Of Death (BSOD), the most simple thing to do is noting the informations on the screen with pen and paper (or grab your DigiCam.. ). Check carefully if there are file names mentioned, they are probably the most important thing here.

If Windows just rebooted the computer by itself without a blue screen, you had a BSOD too but Windows doesn't show them by default. How to turn them on (Windows 10):

Originally Posted by Teh intarwebz

1.Click the Search button, search for and open View advanced system settings.

2. Click Settings in the Startup and Recovery section.

3. Remove the check mark next to Automatically restart, and then click OK.

4. Restart the computer.
Thanks for reading!
Attached Images
File Type: jpg Screenshot 2024-03-29 at 12.09.06.jpg (80.5 KB, 772 views)

Last edited by Ollie; 03-29-2024 at 04:19 AM. Reason: added more dump file info
Ollie is offline  

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT -7. The time now is 02:12 PM.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.