search

bdkjones / CodeKit-1-Old

146 stars 1 forks source link

No crash reports #631

Open zoebogner opened 11 years ago

zoebogner commented 11 years ago

I've been having a few problems with Codekit hanging and crashing. On each restart I get the prompt to send a crash report, however the Me/Library/Logs/DiagnosticReports directory Cokekit asks me a get the report from doesn't contain any Codekit crash files. Never has.

I'm running OS X 10.8.4 on an iMac (mid 2011 27-inch), Codekit version 1.6.2 (however this has been happening for a few versions now). My mac's user account is network-managed without admin rights, though this hasn't been a problem for Flash or Chrome, which have each left crash logs in the DiagnosticReports directory. What other info can I supply to help solve this one?

bdkjones commented 11 years ago

Have you tried resetting the app by quitting it and then relaunching it while holding down the shift key? This will clear out all existing data and give you a fresh start, which may solve the problem if it's a corrupted model file.

On 2013 Jul 02, at 19:10 , Zoe Bogner notifications@github.com wrote:

I've been having a few problems with Codekit hanging and crashing. On each restart I get the prompt to send a crash report, however the Me/Library/Logs/DiagnosticReports directory Cokekit asks me a get the report from doesn't contain any Codekit crash files. Never has.

I'm running OS X 10.8.4 on an iMac (mid 2011 27-inch), Codekit version 1.6.2 (however this has been happening for a few versions now). My mac's user account is network-managed without admin rights, though this hasn't been a problem for Flash or Chrome, which have each left crash logs in the DiagnosticReports directory. What other info can I supply to help solve this one?

— Reply to this email directly or view it on GitHub.

zoebogner commented 11 years ago

I've tried that in the past and it didn't seem to help, but I'm giving it another go now and will post back either way the next time I encounter a crash.

I mentioned this problem in passing to a colleague during the week and he said that his setup isn't generating the crash reports for Codekit either. If we're the only ones experiencing this I guess it must be something peculiar about our project or system setup..?

bdkjones commented 11 years ago

The app may not actually be crashing. That window is displayed anytime the app does not quit normally (during a normal quit, CodeKit marks itself as having quit correctly last time it ran. During startup, that value is checked and that's how the crash screen decides whether or not to display.) If you force-quit the app or if you hard-shutdown your Mac, you'll get that screen the next time you run CodeKit, even though the app did not technically crash.