QIODevice::seek (QTcpSocket): Cannot call seek on a sequential device
Posted: Thu Aug 08, 2019 4:28 pm
In the hope of getting some input on this, can we please address the cause of this issue:
^This terminal pops up on machines running the node, the moment they start rendering a network job. If an unsuspecting user closes the terminal, his node and the job crash.
This issue has been reported several times by different members over the past 3 years:
2018-10-30: Nodes not rendering any more!
2018-10-18: After Win10 Update 2 of 12 nodes do not render anymore
2017-10-18: QIODevice::seek!?
2017-06-13: Maxwell Studio 4 - small annoying things
2016-11-09: v4 Render Node(s) Network Error
Please address.
If currently it isn't possible to solve this, please at least can there be an option to ignore the warning so that no terminal pops up? Maxwell's render times are notoriously long, and thus for many applications network rendering is essential. We've spent a lot of time trying to troubleshoot network rendering, and this is one of the last issues we aren't able to solve.
^This terminal pops up on machines running the node, the moment they start rendering a network job. If an unsuspecting user closes the terminal, his node and the job crash.
This issue has been reported several times by different members over the past 3 years:
2018-10-30: Nodes not rendering any more!
2018-10-18: After Win10 Update 2 of 12 nodes do not render anymore
2017-10-18: QIODevice::seek!?
2017-06-13: Maxwell Studio 4 - small annoying things
2016-11-09: v4 Render Node(s) Network Error
Please address.
If currently it isn't possible to solve this, please at least can there be an option to ignore the warning so that no terminal pops up? Maxwell's render times are notoriously long, and thus for many applications network rendering is essential. We've spent a lot of time trying to troubleshoot network rendering, and this is one of the last issues we aren't able to solve.
