greubel
Visitor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2012
05:20 PM
Socket interrupts hanging
Every once in a while the Roku hangs and I have to reboot (unplug). This usually happens after a long period of inactivity.
Had no idea why, BUT I just caught a trace that had a LOT of "roSocketEvent" interrupts.
My question: Is there any way to associate the id from "id = msg.getSocketID()" to the actual socket ? So that maybe, I could close it ?
Had no idea why, BUT I just caught a trace that had a LOT of "roSocketEvent" interrupts.
My question: Is there any way to associate the id from "id = msg.getSocketID()" to the actual socket ? So that maybe, I could close it ?
1 REPLY 1
greubel
Visitor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-06-2012
02:47 PM
Re: Socket interrupts hanging
Follow on question: I have multiple UDP and TCP sockets open in receive mode.
When I quit the application by hitting the "Home" key, will all the sockets be forced closed ?
This is the only thing I can see that would cause the Roku to go into "brick" mode after a prolonged period of time.
Sometimes it only takes five minutes and then I have to power it off to get back.
Maybe this is a difference being in Developer mode.
When I quit the application by hitting the "Home" key, will all the sockets be forced closed ?
This is the only thing I can see that would cause the Roku to go into "brick" mode after a prolonged period of time.
Sometimes it only takes five minutes and then I have to power it off to get back.
Maybe this is a difference being in Developer mode.