Difference between revisions of "Stability"
| Line 2: | Line 2: | ||
We take crashes very seriously. We want to know as much as we can about what caused it. | 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. | + | 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 [http://www.jrmediacenter.com/download.html]download page], but a newer version may be found on the [http://yabb.jriver.com/interact/ forum]. | |
| − | + | 2. '''Disable plug-ins''' and other third party software 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''', [http://www.jrmediacenter.com/purchase.html reinstall your license]. | |
| − | + | 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. | |
| − | |||
| − | 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. | ||
6. Turn off auto-import. It's under tools/options/libraries. | 6. Turn off auto-import. It's under tools/options/libraries. | ||
| Line 20: | Line 18: | ||
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. | 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. | + | 8. Start a thread on [http://yabb.jriver.com/interact/ 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 | + | 9. Enable logging in MC and '''send us a log''' (to 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". | 10. Examine the logs and search for the word "crash". | ||
[[Category: Frequently Asked Questions]] | [[Category: Frequently Asked Questions]] | ||
Revision as of 17:42, 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 [1]download page], but a newer version may be found on the forum.
2. Disable plug-ins and other third party software 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 log (to 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".
