Page 1 of 1

Bug in Girder plugin - 100% CPU

PostPosted: Wed 14. Oct 2009, 13:48
by ocgltd
I'm running IRserver 6.02.30 (32-bit) on a Linux box with a USB IRTrans connected. I'm also running Girder 5 on a windows 2003 Server box with IRTrans plugin 4.1.4.

All works well - except...when I reboot the Linux box (with the IRserver running), the Girder goes to 100% CPU and won't stop until I kill the process (even after IRserver is back up again). Once I restart Girder all works fine.

This is reproducable (on my systems)....

Re: Bug in Girder plugin - 100% CPU

PostPosted: Wed 14. Oct 2009, 15:29
by IRTrans
Does that also happen if the irserver is closed before reboot ?

We will need to check that - looks like shutdown of the connection does not work correctly.

IRTrans

Re: Bug in Girder plugin - 100% CPU

PostPosted: Wed 14. Oct 2009, 15:58
by IRTrans
We where not able to reproduce this behaviour.

We had a irserver running on a LINUX box together with Girder 5 on XP. When we shutdown the LINUX server Girder reports "connection lost".
Once the server incl. the irserver is running again Girder automatically reconnects. There is no problem with CPU usage (0%).

IRTrans

Re: Bug in Girder plugin - 100% CPU

PostPosted: Sun 18. Oct 2009, 12:58
by ocgltd
I re-confirmed that it happens every time. The problem (girder 100% cpu) also happens if I simply stop the irserver service on the Linux box.

My options for running irserver are:
-loglevel 4 -logfile /var/log/irtrans.log -daemon -timestamp /dev/ttyUSB0

My options (checked) for girder are:
"Connect to irtrans server"
"Include remote name"
"Include device address"


Hopefully these options will let you reproduce it.

Re: Bug in Girder plugin - 100% CPU

PostPosted: Sun 18. Oct 2009, 17:27
by IRTrans
I already tested everything back and forth with lots of different options - no problem, it works fine.

So far no one else mentioned this problem. No idea what to do now.

IRTrans