search

jraebrown / growl

Automatically exported from code.google.com/p/growl
0 stars 0 forks source link

Crash in display controller #512

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
In b2 there is a crash in the display controller. Investigate.

Original issue reported on code.google.com by ch...@growl.info on 31 Jul 2012 at 3:10

GoogleCodeExporter commented 8 years ago 
Crash log attached.

Original comment by ch...@growl.info on 31 Jul 2012 at 3:20

Attachments:

GoogleCodeExporter commented 8 years ago 
I put in a try/catch block to protect against this crash in b3, as well as 
moved a couple calls around to try to minimize when this method is called.  Im 
still not entirely sure how this is getting called in a state where it would 
fail.  It will need to be monitored and investigated further as the try/catch 
only protects against crashing, it won't protect us against zombie or leak 
situations that might arise because of this.
Flagging as WaitingOnUser, although we should keep investigating it regardless.

Original comment by dan...@growl.info on 5 Aug 2012 at 3:30

GoogleCodeExporter commented 8 years ago 
One of our volunteers checked in a possible fix for this, will be in next beta. 
 All my try/catch did was move it up the call chain a bit.

Original comment by dan...@growl.info on 13 Aug 2012 at 11:58

GoogleCodeExporter commented 8 years ago 
No reports of this have shown up in the latest beta. Closing.

Original comment by ch...@growl.info on 27 Aug 2012 at 1:36

GoogleCodeExporter commented 8 years ago 
Growl 2 is released, marking these as fixed.

Original comment by ch...@growl.info on 20 Sep 2012 at 3:16

GoogleCodeExporter commented 8 years ago

Original comment by ch...@growl.info on 11 Jan 2013 at 6:27