Stability: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
[[Category:Frequently Asked Questions]] |
[[Category:Frequently Asked Questions]] |
||
We take crashes very seriously. We want to know as much as we can about what caused it. |
|||
Are you using the most current version? If not, please try it. |
|||
You can do some things that will help us find out why a crash occurred. |
|||
⚫ | |||
In this order, |
|||
Uninstall any third party software. |
|||
1. Please update your player to the latest build available. If a newer version has been released, please try it. For example, if you're using MC12, but MC13 has been released, please try it. The latest known stable build is always on the download page, but a newer version may be found on the forum. |
|||
⚫ | |||
2. Disable plug-ins that you use with MC. We have had problems with bugs in plug-ins causing problems in the past. The Audioscrobbler plug-in, for example, would crash MC if you weren't logged into last.fm. |
|||
Copy your system info from MC help and post it on the forum. |
|||
3. We have also seen problems with Virus Checkers, Pop-up Blockers, and SPAM programs. Please disable these to test. |
|||
Here's a [http://yabb.jriver.com/interact/index.php?topic=24031.0 long list of problems caused by other software or hardware]. Please read from the bottom up, since the newest problems are last. |
|||
⚫ | |||
Turn on MC's logging in Help. After a crash, open the "Previous log" and save it. Look for the word "crash" in the log. Consider posting on Interact with a description and a link to the log or include the last hundred lines or so of the log. |
|||
5. Check the [http://yabb.jriver.com/interact/index.php?topic=24031.0 Weird Problems] thread for possible problems. This thread lists a number of problems caused by other software or hardware. |
|||
⚫ | |||
⚫ | |||
⚫ | 7. Think about any changes you've made to your system; both hardware and software. Crashes can be caused by bad CPU, bad memory, bad drivers, etc. A "blue screen", for example, is a hardware or driver issue. Some machines may not be stable under heavy use. The fact that other software works may mean that the software doesn't use the machine in the same way. If you have more than one stick of RAM, consider using just one at a time in order to test. |
||
8. Start a thread on Interact with details about what version you're using, and the events that lead up to the crash. |
|||
9. Enable logging in MC and send us a crash log (logs at jriver) with a link to your thread. Logging is under MC's Help menu, and there you can also e-mail the logs. |
|||
10. Examine the logs and search for the word "crash". |
|||
[[Category: Frequently Asked Questions]] |
Revision as of 17:14, 9 February 2009
We take crashes very seriously. We want to know as much as we can about what caused it.
You can do some things that will help us find out why a crash occurred.
In this order,
1. Please update your player to the latest build available. If a newer version has been released, please try it. For example, if you're using MC12, but MC13 has been released, please try it. The latest known stable build is always on the download page, but a newer version may be found on the forum.
2. Disable plug-ins that you use with MC. We have had problems with bugs in plug-ins causing problems in the past. The Audioscrobbler plug-in, for example, would crash MC if you weren't logged into last.fm.
3. We have also seen problems with Virus Checkers, Pop-up Blockers, and SPAM programs. Please disable these to test.
4. Reboot, reinstall, reinstall your license.
5. Check the Weird Problems thread for possible problems. This thread lists a number of problems caused by other software or hardware.
6. Turn off auto-import. It's under tools/options/libraries.
7. Think about any changes you've made to your system; both hardware and software. Crashes can be caused by bad CPU, bad memory, bad drivers, etc. A "blue screen", for example, is a hardware or driver issue. Some machines may not be stable under heavy use. The fact that other software works may mean that the software doesn't use the machine in the same way. If you have more than one stick of RAM, consider using just one at a time in order to test.
8. Start a thread on Interact with details about what version you're using, and the events that lead up to the crash.
9. Enable logging in MC and send us a crash log (logs at jriver) with a link to your thread. Logging is under MC's Help menu, and there you can also e-mail the logs.
10. Examine the logs and search for the word "crash".