![]() ![]()
On Mac, saved crash files would be found in /Users/ youruserid/Library/Logs/DiagnosticReports/, with the file extension.FYI that you may have folders for other versions present as well, if you've used past releases of JMP. If you're on Windows, these files are likely saved in C:\Users\ youruserid\AppData\Local\Temp\JMPCrashReports\14, with file extensions. ![]() Sigma client crashing how to#Here's how to determine if you have crash files saved on your computer: Of course, it's always good to check to see if you're in case 3 or 4 above by determining if you have crash files present on your computer that you can email to with your crash scenario details). No matter the case, you can always email information about what you were doing when JMP crashed to Hearing the details of your crash scenario may help them either replicate the crash or match up your description with a known issue. This is relatively rare but can happen if JMP goes down too quickly for the software to capture a report.ģ) You may be experiencing an email client incompatibility with our crash reporting systemĤ) Sending crash reports might be blocked by your IT group (since some systems don't allow emailing of zip files) If you do not see that dialog upon relaunch, then there are a couple of possibilities as to what went wrong:ġ) JMP may have been running for a long time but may not be technically crashing-we call this a hang.Ģ) Your crash may not produce any crash files. It should ask if you want to send your (zipped) crash report to JMP technical support. If JMP 14 crashes, you should get a dialog the next time you launch JMP indicating that JMP has stopped working. We are very grateful to customers who report their crashes and bugs in the software, so thank you for being willing to share! It sounds like you've crashed before, but it wasn't clear how to report it, so here are some details that I hope will be helpful. You asked how to report your crashes and how to find the files. The second last thing: dig and figure out what is happening, it sounds reproducible, when you get to the point where you can ask some specific questions, there so many JSL guru's here who would love to help. (like I said get the most up to date version) The last thing: This is important! Send your crashes to the developers are mining error log data and constantly (about every 6 months, in fact) releasing features and updates to make JMP work better so you can work better. Sigma client crashing update#Click Help, Click About JMP and discover who your internal license admin is and tell them to call their JMP Sales contact to get you the update you need. Thats JMP 15.0, and in a couple of weeks 15.1 will be released. Sigma client crashing upgrade#Most people have JMP license that allows them to upgrade to the current version of JMP. Even if you have a slow internet connection its fast. If you have v14, this is free, just download it and install. If you are running v14, you should be running 14.3, not any other earlier dot release. The second first thing to do, and this is such an easy and important thing. If Data*2 ![]() Subtract from that the size of all the data tables your script is going to open. Next check to see how much available memory you have before you start to run the script. There is likely an operating system issue, or a memory issue you are dealing with.įirst check to see that you are using a current licensed version of your operating system. In my hands v14 and v15 are super stable. Sigma client crashing manual#From manual click through analysis to a lot of scripts to automate things. ![]() So, I just want to disclose that I work for JMP. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |