Tray Monitor

[DaveB]

I have experienced the exact issues that Bob is reporting, but not at all on a regular basis. On the same remote machine that has this issue at times, I also have a strange network issue, which I thought was the culprit. When my router re-generates the leases for the IP addresses of connected items, that machine at times does not pick up the renewal. It stays on line, but has to authorized lease. the issue always resolves itself, but the tray app locks in the process.

[Dean Roddey]

Anything that's acting as a server, and the tray monitor is a server since it's waiting for things to connect to it, should generally be set up with static IP addresses so that that doesn't happen.

[DaveB]

Static or not, leases still expire . All of my computers that host parts of the CQC system are set up as static. My router does not allow you to turn off lease expiration. Some do however.

[Dean Roddey]

There's no DHCP lease involved in a static IP setup. The computer registers itself with the router with the static IP it's set up for locally. It never expires.

[DaveB]

I know. Tell my router that. Even with the static set at the PC and reserved on the router end, it still attempts to expire the lease. It is a Net gear and then issue is documented. Eventually, I will replace the router. That is why I never reported the tray app issue. I assume that Bob is also having some sort of network issue similar to this.

[wuench]

Maybe see if you can load DDWRT (or OpenWRT, or Tomato) on it and save yourself some $$$.

[rbroders]

My touch screens all have static IP addresses, so they don't have a lease.

My router of course does get a lease from my ISP for its external address (WAN IP) at least for its IPV4 address. The routers internal address (LAN IP) is static, of course.

I have never noticed any networking issues with my touchscreen.

I don't suppose Dean has any debugging available for the tray app. A log file perhaps? I just checked and it is still running since last restart. I notice that when I killed the last one it had 27MB of private memory whereas the current running one has only 4MB, so perhaps a resource leak of some kind...

--Bob

[Dean Roddey]

If it's using iTunes, then ongoing interaction with iTunes can raise the memory usage for legitimate reasons, to some level. 27MB is probably high. If it's just app control, then 27MB would be quite high and probably indicative of something leaking that I should look into.

[Dean Roddey]

There's no obvious reason for any leakage in the app control stuff. The obvious candidates are the various queues that stuff is queued up on to be processed. But they are all cleaning up appropriately.

[rbroders]

Hmmm, well its been running for three days now holding steady at 4MB.

--Bob