Page 1 of 1
2.13.32 Crash
Posted: Sun Jul 01, 2018 7:13 am
by scozz76
DOM 2.13.32
Win 10 - main encoder
Win 7 - encode servers (x3)
If an encode server loses connection, the main encoder is likely to crash.
Has anyone else had this problem?
Re: 2.13.32 Crash
Posted: Tue Jul 03, 2018 11:20 am
by Carsten
There have been some code changes lately in that area. I could try testing tomorrow. What you did is exiting the encode server while the master was doing an encode using it?
- Carsten
Re: 2.13.32 Crash
Posted: Tue Jul 03, 2018 2:29 pm
by scozz76
Carsten wrote: ↑Tue Jul 03, 2018 11:20 am
There have been some code changes lately in that area. I could try testing tomorrow. What you did is exiting the encode server while the master was doing an encode using it?
- Carsten
It happened when I had to reboot a server. After the initial crash I tested it a few times with the same result about every 3rd server loss. I waited several minutes between server reboots.
Re: 2.13.32 Crash
Posted: Fri Jul 06, 2018 10:26 pm
by carl
I believe this is fixed in 2.13.34. It would be great if you could test it... thanks!
Re: 2.13.32 Crash
Posted: Mon Jul 09, 2018 4:26 pm
by scozz76
I tried to crash it... It survived
Thanks
Re: 2.13.32 Crash
Posted: Tue Jul 10, 2018 9:48 pm
by Carsten
Now, did the bug survive, or DCP-o-matic master?
Re: 2.13.32 Crash
Posted: Sun Jul 15, 2018 12:24 am
by scozz76
DOM survived - The bug has been squashed