Hi,
Recently, deadline crash our nuke when we submit a job to the farm. The only information from windows have have been to collect is this.
Do you know why it is doing this ?
Fichiers aidant à décrire le problème :
C:\Users\fasavard\AppData\Local\Temp\WERED2C.tmp.WERInternalMetadata.xml
C:\Users\fasavard\AppData\Local\Temp\WER7FD.tmp.appcompat.txt
C:\Users\fasavard\AppData\Local\Temp\WER85C.tmp.mdmp
Lire notre déclaration de confidentialité en ligne :
go.microsoft.com/fwlink/?linkid= … cid=0x040c
Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion :
C:\Windows\system32\fr-FR\erofflps.txt
I attache the concern file to the email.
WER85C.tmp.zip (2.39 MB)
We haven’t heard of our submission script crashing Nuke before. Did anything change recently prior to Nuke crashing? For example:
- Windows update
- Nuke update
- New nuke plugin installed, or updated
- Etc…
Cheers,
No nothing change. Since our first day of production everything is the same.
But it ins’t the first time. We have that probleme since a long time, but we never bother because it wasn’t doing it often. But it got worst over the last few weeks. Sometime too the submitter just get stuck at 50% and stay there until we forceshutdown nuke.
Weird. One change we are making for Deadline 6 is to use the subprocess module instead of popen to launch the deadline submission process. We have see flakiness with popen in the past that we’re not seeing with the subprocess module now. If your problems are at all related to using popen, then in theory they should be solved in Deadline 6.
Ho right thks. We will see on the next version
Fred