search

vieten / sequel-pro

Automatically exported from code.google.com/p/sequel-pro
Other
0 stars 0 forks source link

Crash reporter crashes Sequel Pro! #1175

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Load SP.
2. Didn't shut down correctly last time, so SP crash reporter starts itself
3. crash reporter makes the whole app crash, and produces the attached Apple 
crash log

I'm using the latest version AFAIK, 0.9.9.1

Any ideas much appreciated.

Cheers,
Alex

Original issue reported on code.google.com by a...@audiosupport.co.uk on 6 Sep 2011 at 12:47

Attachments:

GoogleCodeExporter commented 9 years ago 
Hi Alex,

So you're stuck in a loop like this?

Oddly the crash log doesn't show the crashed thread actually doing much.  
However, where we have seen issues similar to this previously, it tends to be a 
console log issue.  Could you try opening up Console.app 
(/Applications/Utilities/Console.app), and see if that loads?  If so, filter by 
Sequel Pro - are there many messages, or only a few?

Thanks!

Original comment by rowanb@gmail.com on 6 Sep 2011 at 12:58

GoogleCodeExporter commented 9 years ago 
Thinking about it - In Console there are some log files like 
"system.log.0.bz2", "system.log.1.bz2" and so on (usually a bit hidden though)

Can you open all of those with Console and view their contents correctly?

Original comment by schlabbe...@gmail.com on 6 Sep 2011 at 3:07

GoogleCodeExporter commented 9 years ago 
As we've seen this a few times on 10.5.8/PPC machines, and it's within an 
Apple-provided system routine, I don't think we can directly do anything to 
address the crashes that routine is causing.  So the fix is to avoid using it 
entirely - which is what I've done in r3417.  This loses us a little bit of 
crash diagnosis utility, but it's worth it to prevent further crashes!

I don't know if you're aware, but we make our development code available to 
test as nightly builds, at http://nightly.sequelpro.com/ .  The next time you 
run into this loop I'd appreciate it if you could fire one of the new nightly 
builds up and see if that addresses the issue; we'll include this in the next 
release.

Original comment by rowanb@gmail.com on 8 Sep 2011 at 11:24

GoogleCodeExporter commented 9 years ago 
Thanks for that. I just downloaded Build 3436, and problem still persists. 
Would you like some logs as per comment 1 and 2?

Cheers,
Alex

Original comment by a...@audiosupport.co.uk on 3 Oct 2011 at 1:49

GoogleCodeExporter commented 9 years ago 
Hi Alex - yes please then, check whether the console loads.  It probably will - 
if so, try and dig out the actual crash logs for Sequel Pro and attach those 
here - or email if you'd prefer.  Does the stack trace still look the same as 
the one in your original comment?

Original comment by rowanb@gmail.com on 3 Oct 2011 at 1:59

GoogleCodeExporter commented 9 years ago 
Hi,

I think I have the same problem.
Here is the crash log with the last nightly build.
Hope this problem will be fixed.
Thanks.

Isaac

Original comment by isaacand...@gmail.com on 17 Nov 2011 at 3:37

Attachments:

GoogleCodeExporter commented 9 years ago 
r3568 disables asl_search on <=10.5.8 to fix this crash.

(It also looks like sandboxed apps can't run asl_search even to find their own 
console messages, so we won't have this option in future, either…)

Original comment by rowanb@gmail.com on 31 Mar 2012 at 4:14