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
Ollie
Super Moderator (no feelings)
 
Ollie's Avatar
 
Join Date: Dec 2007
Location: On or near a dike
Posts: 9,742
Default How to report bugs - read me first before posting!

Thank you for reporting a bug!

How to report bugs:

* Give your report a meaningful title
Use a few descriptive words for a thread title like "[2.59]Crash in WTF.DLL when moving item" or "[3.11]XY action not working" if possible.
* Steps how to reproduce
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.

Quote:
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.


* Post error/crash messages!

This can't be stressed enough: Please include error messages and crash logs. Usually if a crash occurs a window will come up notifying you of the crash. Show details of the crash and take a screenshot of it (or copy the text), and post it here.

Additionally, the crash was most probably logged in Event Viewer. How to get there:

Quote:
Originally Posted by Dingo Kidney

[XP]
Go 'Start Menu->Run' and type EVENTVWR <Enter>. In Event Viewer, open the 'Applications' branch and look for the latest "Error" entries.

[Vista and Windows 7]
Go 'Control Panel'=>'Administrative Tools'=>'Event Viewer'. The Vista Event Viewer has more branches, go 'Windows Logs'=>'Application'.
Since Vista doesn't have a "details" button on its crash notification windows, Event Viewer is the only way to get the needed data here.

Jotting down the time of the crash or creating a fresh crash may help you finding the right error entry. The most important informations there are the faulting module and the fault offset. Post them, please.
OSX:

When the Problem Report window pops up, note which thread number crashed in the header:



Then scroll down to the crashed thread and copy that block to your report/reply. Note that you can often see what part (in this example a plug-in) caused the crash.



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:

Quote:
Originally Posted by Teh intarwebz
Open Control Panel, click 'Performance and Maintenance->System' go to the 'Advanced' tab, click 'Settings' in 'Startup and Recovery' and uncheck 'Automatically Restart' in the System failure section. Now make it crash again and note the information on the handsome blue screen.
* 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:

- Your soundcard/interface type and model
- Your CPU type and/or exact model ("Intel 2.4GHz" = bad. "Core2Duo 2.4GHz" or "AMD dualcore" is better.)
- Amount of RAM
* Create a little project demonstrating the bug
If you see fit, create a little project set up readily 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.
*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.)


Thanks for reading!

Last edited by Justin; 02-09-2016 at 09:09 PM.
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 11:41 PM.


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