2.0.2.8 Issues
TheBurningOr
working' and 'A problem has caused the program to stop working
correctly. Windows will close the program and notify you if a solution
is available.'
The odd thing is that while this dialog box is on the screen, Growl
works perfectly, but as soon as I hit the x button or the 'close
program' button, Growl goes away. I wish I could give more
information on the error, but there aren't any other details I can
see. I'm running Windows 7 and have been using Growl successfully for
many months now.
CoolJazz
issue.
Also been using the program a couple of months without problems but
since the update to 2.0.2, it's unusable because of the issue stated
above.
Brian Dunnington
regards to finding the cause of the error:
1. close Growl if it is running
2. launch Growl from the command line with the debug parameter:
Growl.exe /debug:true
3. wait until the error message appears, then choose Close Program to exit
4. go to the location where Growl stores its user prefs (ex:
%USERPROFILE%\Local Settings\Application Data\Growl\2.0.0.0)
5. find the file called debug.txt and copy and paste its contents here
(or upload the file if that is easier)
thanks for reporting the issue - i am sure we can get to the bottom of
it if you can send me that debug log.
> --
> You received this message because you are subscribed to the Google Groups "growl for windows" group.
> To post to this group, send email to growl-fo...@googlegroups.com.
> To unsubscribe from this group, send email to growl-for-wind...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/growl-for-windows?hl=en.
>
>
Brian Dunnington
Translucent Dark? if so and you manually installed them into your
Program Files location, that might be the cause. i will have to wait
until i see the debug log to be certain, but if you *are* using custom
displays, you can try copying the folder that contains the custom
display from the Program Files/Display directory to the Display
directory located at %USERPROFILE%\Local Settings\Application
Data\Growl\2.0.0.0
TheBurningOr
supported.
3/21/2010 7:30:18 PM PROGRAM FOLDER: C:\Program Files\Growl for
Windows
3/21/2010 7:30:18 PM USER FOLDER: C:\Users\Christopher\AppData\Local
\Growl\2.0.0.0\
3/21/2010 7:30:19 PM ContextMenu Handle: 1114990
3/21/2010 7:30:19 PM TIMESTAMP - Before DisplayStyleManager.Load():
2.167124
3/21/2010 7:30:19 PM Display 'Standard' was loaded successfully
3/21/2010 7:30:19 PM Display 'Standard' handles the 'Standard' display
style
3/21/2010 7:30:19 PM Display 'Smokestack' was loaded successfully
3/21/2010 7:30:19 PM Display 'Smokestack' handles the 'Smokestack'
display style
3/21/2010 7:30:19 PM Display 'Plain' was loaded successfully
3/21/2010 7:30:19 PM Display 'Plain' handles the 'Plain' display style
3/21/2010 7:30:19 PM Display 'Toast' was loaded successfully
3/21/2010 7:30:19 PM Display 'Toast' handles the 'Toast' display style
3/21/2010 7:30:19 PM Display 'Visor' was loaded successfully
3/21/2010 7:30:19 PM Display 'Visor' handles the 'Visor' display style
3/21/2010 7:30:19 PM Settings file 'C:\Users\Christopher\AppData\Local
\Growl\2.0.0.0\displayPluginInfo.settings' does not exist.
3/21/2010 7:30:19 PM TIMESTAMP - After DisplayStyleManager.Load():
2.2601293
3/21/2010 7:30:19 PM TIMESTAMP - Before
ForwardDestinationManager.Load(): 2.2961314
3/21/2010 7:30:19 PM Forwarder 'Bonjour Forwarder' was loaded
successfully
3/21/2010 7:30:19 PM Forwarder 'Manual Forwarder' was loaded
successfully
3/21/2010 7:30:19 PM Forwarder 'Prowl' was loaded successfully
3/21/2010 7:30:19 PM Forwarder 'Twitter' was loaded successfully
3/21/2010 7:30:19 PM Forwarder 'Email' was loaded successfully
3/21/2010 7:30:19 PM TIMESTAMP - After
ForwardDestinationManager.Load(): 2.3551347
3/21/2010 7:30:19 PM TIMESTAMP - Before SubscriptionManager.Load():
2.3651353
3/21/2010 7:30:19 PM Subscriber 'GNTP Subscription' was loaded
successfully
3/21/2010 7:30:19 PM Subscriber 'Notify.io' was loaded successfully
3/21/2010 7:30:19 PM Settings file 'C:\Users\Christopher\AppData\Local
\Growl\2.0.0.0\subscriberPluginInfo.settings' does not exist.
3/21/2010 7:30:19 PM TIMESTAMP - After SubscriptionManager.Load():
2.3821363
3/21/2010 7:30:19 PM FINAL LOAD TIME: 2.4531404
3/21/2010 7:30:19 PM idle timer stopped.
3/21/2010 7:30:19 PM idle timer stopped.
3/21/2010 7:30:19 PM Settings file 'C:\Users\Christopher\AppData\Local
\Growl\2.0.0.0\sysnot.list' does not exist.
3/21/2010 7:30:20 PM The plugin at 'C:\Users\Christopher\AppData\Local
\Growl\2.0.0.0\Displays\Chrome Twitter Display' could not be loaded.
System.TypeLoadException: Method 'CancelClosing' in type
'ChromeTwitterDisplay.FadeAnimator' from assembly
'ChromeTwitterDisplay, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=null' does not have an implementation.
at System.Reflection.Assembly._GetExportedTypes()
at System.Reflection.Assembly.GetExportedTypes()
at Growl.PluginFinder.Search[T](String path, TypeFoundDelegate del,
List`1 ignoreList)
3/21/2010 7:30:20 PM Bonjour service detected: Growl on CHRISTOPHER-
WIN
On Mar 21, 6:38 pm, Brian Dunnington <briandunning...@gmail.com>
wrote:
> also: are either of you running any additional displays, such as
> Translucent Dark? if so and you manually installed them into your
> Program Files location, that might be the cause. i will have to wait
> until i see the debug log to be certain, but if you *are* using custom
> displays, you can try copying the folder that contains the custom
> display from the Program Files/Display directory to the Display
> directory located at %USERPROFILE%\Local Settings\Application
> Data\Growl\2.0.0.0
>
> On Sun, Mar 21, 2010 at 6:34 PM, Brian Dunnington
>
>
>
> <briandunning...@gmail.com> wrote:
> > if either of you could do the following, it would help out a ton with
> > regards to finding the cause of the error:
>
> > 1. close Growl if it is running
> > 2. launch Growl from the command line with the debug parameter:
> > Growl.exe /debug:true
> > 3. wait until the error message appears, then choose Close Program to exit
> > 4. go to the location where Growl stores its user prefs (ex:
> > %USERPROFILE%\Local Settings\Application Data\Growl\2.0.0.0)
> > 5. find the file called debug.txt and copy and paste its contents here
> > (or upload the file if that is easier)
>
> > thanks for reporting the issue - i am sure we can get to the bottom of
> > it if you can send me that debug log.
>
TheBurningOr
Twitter Display) which I had deleted from within Growl, but evidently
had no deleted the actual folder in the displays directory. I deleted
that and it works fine now.
Brian Dunnington
i also saw a report on Twitter that the Chrome Twitter display wasnt
working for someone else as well, so i tried installing it and got the
same issue. glad to hear it is working again for you, and hopefully
anyone else with this issue will be able to solve it as well.
(for anyone that is interested: in versions prior to 2.0.2.8, each
individual display required GfW to reload all of the common plugin
assemblies for each individual display. this was good in that it
allowed each display to provide their own version of the common
assemblies, but it was bad because lots of duplicate code was being
loaded and retained in memory. as of 2.0.2.8, all display plugins
reference one set of common assemblies, so the duplicate overhead is
removed. however, in the case of Chrome Twitter, it was using a very
old version of the common assemblies that was not compatible with the
new common assemblies. i thought i had verified that every custom
display still worked with the new version, but i overlooked that one,
so i take full responsibility for the bug).
CoolJazz
tnx