2.13.32 Crash

Anything and everything to do with DCP-o-matic.
scozz76
Posts: 70
Joined: Sun May 15, 2016 10:13 am

2.13.32 Crash

Post 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?
Carsten
Posts: 2804
Joined: Tue Apr 15, 2014 9:11 pm
Location: Germany

Re: 2.13.32 Crash

Post 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
scozz76
Posts: 70
Joined: Sun May 15, 2016 10:13 am

Re: 2.13.32 Crash

Post 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.
carl
Site Admin
Posts: 2550
Joined: Thu Nov 14, 2013 2:53 pm

Re: 2.13.32 Crash

Post by carl »

I believe this is fixed in 2.13.34. It would be great if you could test it... thanks!
scozz76
Posts: 70
Joined: Sun May 15, 2016 10:13 am

Re: 2.13.32 Crash

Post by scozz76 »

I tried to crash it... It survived
Thanks
Carsten
Posts: 2804
Joined: Tue Apr 15, 2014 9:11 pm
Location: Germany

Re: 2.13.32 Crash

Post by Carsten »

Now, did the bug survive, or DCP-o-matic master? 8-)
scozz76
Posts: 70
Joined: Sun May 15, 2016 10:13 am

Re: 2.13.32 Crash

Post by scozz76 »

DOM survived - The bug has been squashed :)