Quick Sign In:  

Forum: Old versions

Topic: Read me first : tips for reporting a bug/crash/freeze

This topic is old and might contain outdated or incorrect information.

sbangsPRO InfinityMember since 2004
1. please check the forum to see if there is already a fix for your problem :)

software - http://www.virtualdj.com/forums/20/Software_Technical_Support.html
hardware - http://www.virtualdj.com/forums/31/Hardware_Technical_Support.html

2. If you get the recover window with the yellow smilley, please copy and paste the data of your "crashguard report.txt" file on the forum with a description of the problem.
(this file is in My documents -> VirtualDJ. Open it with Wordpad and not Notepad)
(As soon as the data are written on the forum, please delete the file)

3. Please check that the bug re-occurs and was not a one off freak occurance

4. Please be as specific as possible, give details , such as what you were running at the time, what your pc specs are , how often it occurs , when did it start, which version of VirtualDJ you are using

if you are not specific, it will be difficult to help you :)

NB:
We tell there is a crash when the software shuts itself down, and NOT when the software freezes or when you have to force quit the software.

Microsoft wrote :
One of the major causes of frustration between developers and users is the fact that many bugs cannot be reliably reproduced. If they can’t be reproduced, they cannot be easily fixed. This leads to animosity between developers and users and wastes time as users try to reproduce the bug and developers try to find a non-reproducible bug.

A common reason bugs are not reproducible is the quality of the bug report. Bug reports take time to properly create even when there is sufficient information. In many cases, there isn’t sufficient information or the user cannot remember everything he did. This is particularly noticeable when a user is performing exploratory testing and doesn’t have a defined series of steps.

When a bug is caused by specific environment settings, it becomes that much more difficult to reproduce. When one setting in one environment causes a problem, the chances of reproducing it are very slim without access to that specific environment. There are many reasons for this but the most obvious is that the developers don’t know any of the characteristics of the machine on which the test was run or have access to that machine.


a very good article on crash report
 

Posted Fri 03 Nov 06 @ 6:02 pm
djcelPRO InfinityModeratorMember since 2004
And we advise you to watch this video:
 

Posted Sun 31 May 15 @ 10:42 am


(Old topics and forums are automatically closed)