What steps will reproduce the problem?
1. Start boblightd
2. Start client
3. wait 1 min and stop client.
What version of the product are you using? On what operating system?
I'am using it on a mipsel box (et9000)
Please provide any additional information below.
When i start my client and wait for 1 or 2 min and stop.
I look in the cpu stats and see directly that boblight go from 20-30% to 3-5%
Now ik wait 30sec and boblight goes to 15% cpu, and there is no client
connected on this moment. Strange problem.
Other problem is when i at boblightd in bootup, then it will hang with 60-70%
cpu. i need to kill them.
I compile the daemon with the mhard-float and -O3 flag.
DO you have any idea how i can fix this problems or do i need some other
compiler flags.
Kind regards Martijn
Original issue reported on code.google.com by boblight...@gmail.com on 25 Feb 2013 at 12:55
Original issue reported on code.google.com by
boblight...@gmail.comon 25 Feb 2013 at 12:55