Seems like a memory leak.

[joewski]

Hi I was using a program called Stumble upon which recommend your software.
Anyway I just installed it and after about five minutes a string of dialog boxes starts to appear claiming the application is unable to access a memory address.

Any ideas as to what may be causing this?

[mouser]

oy..
it must be the latest routine i added yesterday to have the tiny tray tool launch the gui program to show the about box and on startup, has a bug because the program has been rock solid for months.

let me guess, it happened right on start up or else when showing about box?

[mouser]

hmm.. im rereading your post now that its happening after about 5 minutes so that sounds like its not what i thought..
anyone else experiencing this?  it has to be something with the latest build..

[mouser]

if anyone else can confirm they are experiencing this please let me know and i'll re-upload the last stable version asap.

[bob666]

if anyone else can confirm they are experiencing this please let me know and i'll re-upload the last stable version asap.

-mouser (August 26, 2005, 04:48 AM)

yes... i just dl'ed it and i have this exact problem (wXP sp2 all updates)

[mouser]

do either of you have any clue what might be causing this?
any hint about what triggers it?

bob - it ran for a while and then showed this? did you do anything right before it happened?

it's really strange because i and *many* people run this tool 24hrs a day, 7 days a week, for months and never seen this.

is it possible that it's trying to tame some specific process that triggers the problem?
can you reproduce the crash reliably?

[m_s]

I run it 24/7 on two laptops - both XP SP2 - without any problems...

[bob666]

do either of you have any clue what might be causing this?
any hint about what triggers it?

bob - it ran for a while and then showed this? did you do anything right before it happened?

it's really strange because i and *many* people run this tool 24hrs a day, 7 days a week, for months and never seen this.

is it possible that it's trying to tame some specific process that triggers the problem?
can you reproduce the crash reliably?

-mouser (September 17, 2005, 04:22 AM)

well, maybe i was premature with the post mouser. it only happened when i installed it, an d not since. it has been running about half and hour during this testing phase. when it did it, i received 3-4 boxes with the above mentioned error. it otherwise works flawlessly and as avertised. i will have to see if this is something that happens upon installation or upon initial execution. thankyou for responding so soon, i wan't counting on it, haha.

[mouser]

well happening once is much too much.
did it happen right when it started? or was it after a delay of several minutes?

[bob666]

there was quite a delay actually. about 2 minutes, that's why it surprised me. not being a programmer, i thought it was maybe something wrong on my part. i have balloon tips disabled on my system because i don't like them, so after i saw all these error boxes appear, i pressumed that it was the program trying to do what it is supposed to do (show a balloon). i just disabled the show balloons option. now as to whether this is why the error boxes have not returned or some other reason, i don't know. i will keep this page logged on so i can communicate with you if you want.

[mouser]

interesting idea, though it shouldn't be the case that trying to show a balloon when they are disabled in windows should cause an error like that, such a thing might explain why so few people experience this (since most dont have balloons turned off).

if joewski sees this, maybe he could tell us if he also has balloon's turned off in his windows installation.

do you think there might have been an application using a lot of your cpu at the time of the error, which process tamer was trying to tame at the time?

if you would be willing to do some tests, with balloon messages turned on and off in process tamer while using an app that uses too much of the cpu (try the included cpueater test utility), i'd really appreciate any clues you might find to reproducing the error.

[bob666]

okay, i'll do the testing for you this weekend. i really don't know if the ballons have anything to do with it, but it will be easy enough to see by this sunday. i manufacture pc's and it's pretty hard for my own personal pc to ever act up, but i noticed that while using firefox with several open tabs, cpu usage goes up on pages that automatically reload if i have about 20-30 tabs open. and when i use limewire pro, cpu usage goes up depending on the amount of open connections on a T-1. exiting firefox or limewire never helped, so i decided to test your software. now when i installed it, i had just rebooted my machine for the first time in about 2 weeks and had ran nothing (with the exception of the apps that start with my pc, so i'll list them, who knows, it may help:

Zone Alarm Pro (big cpu hog depending on the circumstances, but i can't afford Outpost)
System Suite 5 (has a Trend Micro anti-virus)
Cacheman XP
Protowall
Peer Guardian
Spybot Search and Destroy (the Tea Timer app)
Yahoo Messenger
AIM messenger

an always on T-1 connection

your app

that amounts to a tray full of icons. i have 2 gigs of memory, and with them all running including firefox with 23 tabs open, i have 1.68 gigs memory free. i use an asus board with an amd 64 x2.

hope that might give you some info to go on. i really don't think anything needed to be tamed at the time. no instant messaging was going on, and at the time, the browser was fine. now the big thing that does start to move the cpu bar up is the vsmon.exe module of Zone Alarm. yes i use a suite version of that app. vsmon cpu use goes up exponentially while limewire pro is on or firefox is many  tabbed and rowdy. vsmon will also claim a large memory footprint that can be very high. closing these apps doesn't help. Cacheman XP can be used to reclaim memory, but the memory it get's back is almost always from XP, not the offending apps. the CPU footprint is another matter and that is why i was happy to learn of process tamer.

all stuff was not going on at the time, but they typically do on this box. i'll try to narrow it for you by sunday.

[zridling]

Check out Veign's new Usage Monitor (donationware). If you note the GDI numbers, they will point you to any memory leaks. I use it for just that purpose to report back to developers. With some, it seems to happen every other version for some odd reason.