search

richdesigns81 / growl

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

Potential crash involving bartender #530

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. We have seen crash reports we cannot readily explain, but all contain 
Bartender in their loaded images
2. Some report involving display add/removal as being part of the problem
3. Crash

What is the expected output?
That Growl should continue to work
What do you see instead?
That Growl crashes

Please use labels and text to provide additional information.
We aren't entirely sure of the cause, and I have been unable to reproduce it, 
but having it not running definitely stops the crash for users, so it is at 
least partially involved.

Original issue reported on code.google.com by dan...@growl.info on 24 Sep 2012 at 6:41

GoogleCodeExporter commented 8 years ago 
For reference: http://macbartender.com

Original comment by dan...@growl.info on 24 Sep 2012 at 6:41

GoogleCodeExporter commented 8 years ago 
Growl 2.0 crashes when launching Aperture 3.4 with Bartender ON.
Growl 2.0 DOES NOT crash when launching Aperture 3.4 with Bartender OFF

Original comment by thierry....@gmail.com on 24 Sep 2012 at 6:54

Attachments:

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Monitor unplug crash log.

Original comment by pariahw...@gmail.com on 24 Sep 2012 at 7:10

Attachments:

GoogleCodeExporter commented 8 years ago 
Growl 2.0 crashes when plugging OR unplugging a 27" Apple Cinema Display 
(DisplayPort) with Bartender running
Growl 2.0 DOES NOT crash when plugging OR unplugging a 27" Apple Cinema Display 
(DisplayPort) with Bartender OFF

Original comment by thierry....@gmail.com on 25 Sep 2012 at 6:51

Attachments:

GoogleCodeExporter commented 8 years ago 
We've reported this one to the bartender folks.

Original comment by ch...@growl.info on 25 Sep 2012 at 5:51

GoogleCodeExporter commented 8 years ago 
We're not blocking this on any milestone. Once the bartender folks get back to 
me, I'll update the ticket.

Original comment by ch...@growl.info on 2 Oct 2012 at 5:02

GoogleCodeExporter commented 8 years ago 
failing a resolution from bartender regarding this, recommend we throw up a 
dialog if we detect bartender code being injected into our process.

Original comment by rarich...@gmail.com on 4 Dec 2012 at 10:26

GoogleCodeExporter commented 8 years ago 
Issue 568 has been merged into this issue.

Original comment by rarich...@gmail.com on 4 Dec 2012 at 10:27

GoogleCodeExporter commented 8 years ago 
Hi guys, Its Ben here the developer of Bartender, I just wanted to let you know 
I am looking into this issue now as top priority, I thought we had fixed the 
earlier Growl issues with a previous fix, I have recreated the crash mentioned 
in Issue 568 and seem to have fixed that here also, but I want to make sure I 
am not just pushing the issue deeper etc.

Original comment by BenSurtees on 5 Dec 2012 at 5:23

GoogleCodeExporter commented 8 years ago 
Released Bartender version 1.0.6 on Monday (10th Dec), which should fix the 
issues caused by Bartender.

Original comment by BenSurtees on 13 Dec 2012 at 5:32

GoogleCodeExporter commented 8 years ago 
Im closing this as done, if others have issues in the future, we can look at 
this again

Original comment by dan...@growl.info on 28 Apr 2013 at 8:48