search

trikon / growl

Automatically exported from code.google.com/p/growl
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Bezel style crashes Growl #278

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Playing enough with Bezel style crash Growl.

What steps will reproduce the problem?
1. Open Preferences.
2. Go to Bezel style (my default is Smoke).
3. Press Preview and change style intermittently (please see attached screen 
recording).

What is the expected output?

Do not crash.

What do you see instead?

Growl crashing.

What version of the product are you using? On what operating system?

1.3 b3 on Lion 10.7.1

Please provide any additional information below.

I managed to crash Growl reliably, it's just the amount of clicks required 
changes. Also, it might be related to Preferences window move, I moved it on 
purpose in recorded clip.

Original issue reported on code.google.com by Ivars.St...@gmail.com on 19 Sep 2011 at 9:00

Attachments:

GoogleCodeExporter commented 8 years ago 
Although much harder (I had to press preview about 30x), I managed to crash 
Growl the same way on my other Mac. Crash report attached.

Original comment by Ivars.St...@gmail.com on 19 Sep 2011 at 3:01

Attachments:

GoogleCodeExporter commented 8 years ago 
To be honest, unless you can reproduce this with a more normal use case, we 
won't be investigating this. Users aren't (likely) going to continually 
repeatedly swap settings on styles while also spamming the preview button.

Original comment by dan...@growl.info on 19 Sep 2011 at 4:43

GoogleCodeExporter commented 8 years ago 
I'd never noticed this problem if it required 30 clicks. But it's easy to crash 
Growl with just a few. Actual case use was simple - I was testing Bezel style 
and could not decide if I like normal or charcoal style. I guess it takes 30 
clicks on a powerful Mac, but on a slower one Growl sometimes crashes on the 
third click...
Anyway, it's entirely up to you.

Original comment by Ivars.St...@gmail.com on 19 Sep 2011 at 4:51

GoogleCodeExporter commented 8 years ago 
Let's see if anyone else finds this to be a problem with 1.3 out in the wild. 
That'll be the determining factor.

Original comment by ch...@growl.info on 19 Sep 2011 at 4:55

GoogleCodeExporter commented 8 years ago 
Possibly related: #157 and #162.

Original comment by boredzo on 19 Sep 2011 at 11:20

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
This *is* a real problem you can find in the wild: I use bezel for system 
notifications (HardwareGrowler, changed network settings, ...) and another 
style for app notifications (updates, downloads, new mail, new message, ...) => 
whenever a system notification and an app notifaction are fired simultaneously 
(which in fact is every time I start my Mac or run my Windows emulator), growl 
crashes.

(Growl 1.3.3, Lion 10.7.4)

Original comment by Sirk...@gmail.com on 25 May 2012 at 3:48

GoogleCodeExporter commented 8 years ago 
So you can reproduce this pretty regularly?

Original comment by ch...@growl.info on 26 May 2012 at 2:32

GoogleCodeExporter commented 8 years ago 
Yes. I think at least three times a day can be called 'pretty rugularly' ;)

Original comment by Sirk...@gmail.com on 26 May 2012 at 6:41

GoogleCodeExporter commented 8 years ago 
2 things then:

1) Can you get us an actual crash log?

2) Would you be willing to try out the beta?

Original comment by ch...@growl.info on 26 May 2012 at 9:10

GoogleCodeExporter commented 8 years ago 
1) If you could tell me how to do that, I'd be happy to do so.

2) Sure. :) ... (as long as I don't have to compile anything)

Original comment by Sirk...@gmail.com on 27 May 2012 at 7:03

GoogleCodeExporter commented 8 years ago 
1) Look in Console (an application located in Applications -> Utilities). See 
if there's anything saying Growl crashed when this happens. 

2) Email me. chris@growl.info and no there is no compiling involved. We do ask 
for constructive feedback. :)

Original comment by ch...@growl.info on 27 May 2012 at 7:57

GoogleCodeExporter commented 8 years ago 
This crash is in the very messed up positioning window controller and 
positioning controller system, as well as the basic flaws in how queuing 
displays are designed.  2.0 will bring significant changes and improvements to 
these, and till it enters testing sometime after 1.4 ships (I have abused bezel 
and other queuing displays quite thoroughly and seen no crashing), closing this 
again as FixedInSource this time.

Original comment by dan...@growl.info on 28 May 2012 at 3:07

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