SWRemote instance remains loaded in memory after quiting

yaccri · Post by **yaccri** » Mon Sep 13, 2004 6:57 am

When exiting SWRemote (using the 'Exit Remote' button), the windows task manager shows that the process is still running. I end up having many instances of SWRemote. When closing the HouseBot server though, all the SWRemote processes get closed also.

Also, the bug of deleting an image control that causes HB to crash is really annoying.

Are you going to release bug fixes soon? I miss the old days of Scott's same day's fixes

Thanks,

Yoram.

Post by **ScottBot** » Mon Sep 13, 2004 8:56 am

It sounds like the socket connection to the server isn't being closed for some reason. If you turn on tracing on the SWRemote (from the configuration dialog), can you send me the trace file?

yaccri · Post by **yaccri** » Mon Sep 13, 2004 9:06 am

Hi Scott,

Here is the TraceLog.txt

--------------------------

9/13/2004 15:25 - Last Heart Beat At

9/13/2004 15:25 - Attempting to connect to the server

9/13/2004 15:25 - Client is attempting to connect to the server

9/13/2004 15:25 - Battery Percentage = 20, Sleep Timeout = -1

9/13/2004 15:25 - Logging in to Server

9/13/2004 15:25 - Connected to the server

9/13/2004 15:25 - Login Successful.

9/13/2004 15:25 - Checking Theme file for updates...

9/13/2004 15:25 - Checking Theme file dependencies for updates...

9/13/2004 15:25 - Loading Theme

9/13/2004 15:25 - Initializing Panel [- First Panel -]

9/13/2004 15:25 - Initializing Panel [Buttons Only]

9/13/2004 15:25 - Initializing Panel [DVD]

9/13/2004 15:25 - Initializing Panel [VCR]

9/13/2004 15:25 - Initializing Panel [Lighting-Room1]

9/13/2004 15:25 - Initializing Panel [Lighting]

9/13/2004 15:25 - Initializing Panel [VCR - 1]

9/13/2004 15:25 - Initializing Panel [Functions]

9/13/2004 15:25 - Initializing Panel [ShalatDVD1]

9/13/2004 15:25 - The Client is closing and disconnecting from the server.

9/13/2004 15:25 - send() failed: error Either the application has not called WSAStartup, or WSAStartup failed.

---------------------------------------------

Post by **ScottBot** » Mon Sep 13, 2004 10:29 am

It looks as though the client is attempting to send data to the server after it has closed the connection (not a good thing to try). While the problem is fixable in code, I'm curious to know why this is happening.

Do you have anything in the Panel exit list that is open when the SW Remote is closing? Or maybe something else that might cause the SW Remote to try and send something to the server at the last moment?

yaccri · Post by **yaccri** » Mon Sep 13, 2004 11:44 am

Do you have anything in the Panel exit list that is open when the SW Remote is closing? Or maybe something else that might cause the SW Remote to try and send something to the server at the last moment?

Not at all. Actually this theme I'm working on is doing nothing (only new UI design test).

Could it come from a plugin? There is one plugin I developed in version 1.x and just carried it over to version 2.x without making any changes. I don't use it in the theme, but it is loaded with HB.

Is there a way to check it?

Thanks,

Yoram.

Post by **ScottBot** » Mon Sep 13, 2004 2:01 pm

I'm pretty sure that the plugin won't cause this. The problem is that the Software Remote is trying to send something to the server after it has disconnected.

If you could create a sample config that includes the theme (or a variation of the Theme that you might want to slim it down as small as possible) and send it to me so I can reproduce it, it would be helpful.

yaccri · Post by **yaccri** » Mon Sep 13, 2004 2:34 pm

There isn't much to send. For the test, I created a new theme and put only an 'Exit Remote' button on it. Nothing else is there. The SWRemote process is still running after quiting.

It must be something other then the theme.

One more thing to mention. I don't suppose that this is the cause, but who knows? (you of course). When HB is loaded, I get two error messages (because I don't have a COM2 port):

1. Error initializing ... GenericSerial.dll

2. Unable to open Com port (2).

Any ideas?

Thanks,

Yoram.

Post by **ScottBot** » Mon Sep 13, 2004 4:57 pm

I've not seen this with a simple configuration like you mentioned. I'll look into a bit more, but nothing is coming to mind.

You should be able to disable the Generic Serial Interface that is generating the error messages to stop the errors.

yaccri · Post by **yaccri** » Mon Sep 13, 2004 5:07 pm

I disabled the Generic Serial interface, but it didn't help with the SWRemote issue.

Post by **ScottBot** » Mon Sep 13, 2004 10:23 pm

Are you seeing this when running from the local machine, or only remotely?

yaccri · Post by **yaccri** » Tue Sep 14, 2004 1:42 am

That is interesting. The problem appears only when working localy on one PC. I'll investigate it further and post the findings.

Thanks,

Yoram

yaccri · Post by **yaccri** » Wed Sep 15, 2004 5:03 am

Scott,

Just to be sure, I installed the plugin and a device that uses ut on the other PC. You were right (as always) stating that you're

pretty sure that the plugin won't cause this

. It had no effect on SWRemote that shutting down properly on that machine.

One other thing that may worth mentioning: When upgrading to meedio HB on the laptop (the machine that experiencee the problem), I made registry changes as you adviced. The other PC had a clean install.

Does it matter? Should I check any registry settings?

Thanks,

Yoram

Post by **ScottBot** » Wed Sep 15, 2004 8:55 am

I don't know of any registry settings that would cause this. If you want to make sure, you can delete (or just rename so you can switch back) the entire HKLM\Software\Meedio\HouseBot\HouseClient key. The next time you start the SWRemote on that machine, it will prompt for the connection info to the server.

What kind of machine/OS is this running on?

yaccri · Post by **yaccri** » Thu Sep 16, 2004 2:14 am

Renaming the registry entry didn't help. SWRemote is still in memory.

What kind of machine/OS is this running on?

It runs on a Toshiba 2.2MHz pentium 4M laptop with 512Mb RAM and WIN XP Pro.

Thanks,

Yoram