Re: [Gnash-dev] ExternalEventCheck selects w/100us timeout

2010-08-06 Thread Rob Savoye
On 08/05/10 20:13, John Gilmore wrote: If this code is only called 50 times a second or something (whatever the frequency of the main loop is), then it should just poll the file descriptor with select or FIONREAD. It appears to do the FIONREAD anyway, so might as well entirely remove the

Re: [Gnash-dev] ExternalEventCheck selects w/100us timeout

2010-08-06 Thread John Gilmore
If this code is called more frequently than that, it should probably use the main select() loop (and create a main select() loop for the framebuffer GUI, there are good reasons why every other GUI does this). I'll think about for the framebuffer GUI post release, as I'll be doing other

Re: [Gnash-dev] ExternalEventCheck selects w/100us timeout

2010-08-05 Thread John Gilmore
We could drop the select(), or reduce the timeout, but as this is a reasonably new feature, I seriously doubt it's been a big performance problem. If this code is only called 50 times a second or something (whatever the frequency of the main loop is), then it should just poll the file

[Gnash-dev] ExternalEventCheck selects w/100us timeout

2010-08-04 Thread John Gilmore
I'm poking into the cause of CPU time going to 100% while running gnash. I posted some hints a week or two ago, but nobody followed up on them, so I'm seeing if there's something simple that I can fix. I'm having trouble figuring out why ExternalEventCheck is polling with select() and a very

Re: [Gnash-dev] ExternalEventCheck selects w/100us timeout

2010-08-04 Thread Rob Savoye
On 08/04/10 21:55, John Gilmore wrote: I'm having trouble figuring out why ExternalEventCheck is polling with select() and a very short timeout every time around the movie_root loop to see if a browser wants to talk to it over a file descriptor. We could drop the select(), or reduce the