Hardware latency tests, used PC's

tommylight wrote:

- Default run, works, exist on latency over 25000 as it should,
- Run with no base thread exits properly,
- Run with no base thread when pressing ctrl+c doe snot exit, see bellow,
- Run with base thread at 100000 does not exit cleanly,
- Run with base thread at 100000 when pressing ctrl+c does not exit, see below

----This is the bellow part:
After ctrl+c the terminal will continuously show this:

X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  3 (X_GetWindowAttributes)
  Resource id in failed request:  0x5c00002
  Serial number of failed request:  18
  Current serial number in output stream:  19

It does not exit after several ctrl+c, has to be terminated.
So so close....

I'll look into this. Works here. Must have to do with closing the browser window and the xdotools.
greez
chris

kill -SIGINT $(ps -A | awk '/latency/{print $1}')

should terminate latency still running in bg

I can reproduce the errormessages. It seems to be a race condition in xdotool, see here

lcnc-hw closes the browserwindow in my case, but I >think< xdotool "thinks" it is not.

You can do the following:

Hope I got it sorted out now. Kindly let me know.

Edit: could be that sometimes the browser window is not closed automacilly. But now the odd error messages should be gone for good

Kindly be more specific on where it is not cleanly exiting. I have it stopping everyting nicely here, only the browser window sometimes does not close. This is the behaviour that is described in the race condition problem of xdotool. I cannot fix that. Useers will have to live with than and bite sour apple by closing the eventually still running vimeo by hand.

greez chris

PS: be sure to post a link on the new thread here

Welcome. About the new thread: is it on my script or the intention of it gathering comparable hw and latency data? Two threads probably.
greez
chris