Fatal IO error: client killed. Silent crash and this is the only hint I have.
-
It is steady throughout the run of the app when we're watching it. However, since it can run for hours without any problems, and we have no indication of why it fails, we haven't seen it fail. We only see it has failed after the fact. Also, if it is leaking memory, I think that would show up in a log somewhere, correct? We haven't seen anything to indicate memory is the issue.
-
Hi and welcome to devnet,
Can you try with a more recent version of Qt ? 4.7.3 is rather old
-
I didn't mean that you should replace it right away, just if you can test it with a new version in your test environment to see if it still happens. If not then there might have been a bug that's been fixed in between
-
I'll keep it in mind for eventual test scenarios if what I have in mind right now proves fruitless. Version changes would be a huge deal for us.
For additional info, and probably something I should have included before, we run this on an Xvnc display for remote viewing. We start an XVnc server and then start our app on a vnc display. Is it possible that an issue between my app and the Xvnc server is causing this?
-
That's a possibility yes, maybe network glitches… Did you took a look at the "bug report system":http://bugreports.qt-project.org to see whether there's something about it ?
-
This "one":https://bugreports.qt-project.org/browse/QTBUG-17888 was the closest one, but there is no resolution and I am not seeing any resource leakage.
-
Just a crazy idea… Do you have a screen saver that is triggered ? These might have unsuspected side effects
-
i am facing a similar issue with a Qt3 application. Have you ever found out what the problem was?
-
I have finally found the reason for the issue, its a sequence number wrap-around bug in the libX11: http://stackoverflow.com/questions/23871516/xreply-terminates-app-with-xioerror
