BurnInTest Linux V5 1017 Network disconnect causes GUI to hang

[FraceR]

Hi,

We've ran into an issue where the GUI for BurnInTest stops updating when the network connection is lost (in this case cable is disconnected during test). It will no longer update the main window or any of the test displays and does not respond to the 'stop' button. When we reconnect the cable after about 30 to 40 seconds the interface will update and respond again. During this time all the tests appear to have still been running, making me believe the problem is with the GUI thread specifically.

We have tried replicating the issue with debug mode enabled (bit_gui_x64 -d) but then this issue does not show itself and the interface stays responsive. BurnInTest for Linux V4.1 1002 does not have this issue either.

We have 2 test environments in use at the moment, one based on Fedora 39 LXDE with kernel version 6.7.4-200-fc39.x86_64 and Fedora 41 LXDE with kernel version 6.13.9-200.fc41.x86_64. Both of these show the same behaviour with BurnInTest.

Could you perhaps share a way to resolve this that would not involve enabling debug mode for testing.

Thank you.

[Simon (PassMark)]

What tests were you running? Standard/Adv network test? Other tests? Can we get your config?

Tried running BIT Linux on Fedora 41 LXDE but was unable to reproduce your issue. (though I was unable to detect/connect to Endpoints for the Adv network test - maybe something is missing in the LXDE version)
Also tried Fedora 41 Workstation but again was unable to reproduce your issue.

[FraceR]

Hi Simon,

Thank you for your time. I've uploaded the test configuration that was causing issues:

The network test was the standard test with the 'Test all available NICs' option checked. We've found that Adv network test will work but requires fiddling with the firewall settings.

The problem is more pronounced on some systems than it is on others. Most of the higher end configurations seem unaffected. Should we perhaps look at our duty cycle settings?

Best regards,
Frank

PS.
I think I've found where our problem might have been stemming from. We're storing the test results on a network drive, could it be it's trying to log the error to the result file and not being able to write and hang?

[Simon (PassMark)]

If you disable logging, does it run ok when you disconnect network?

Don't have a network drive to test with - can you try the below build, made some changes to try and address the issue:
https://www.passmark.com/downloads/t...0250417.tar.gz

[FraceR]

Yes, then it runs fine when storing locally or not at all. I guess that's why running in debug mode it did not show this issue, it changed the logging location.

Thank you for the other build. As far as I've tested that no longer freezes when network connection is lost for some reason.