I would suggest extracting the zip to C:\TEMP and run procmon.exe. You have to be an administrator on the computer in order for Process Monitor to run. This is an executable program and does not install on the computer.
Google search “Process Monitor” and download it only from the site. The 'go to' program to capture file contention is Sysinternals Process Monitor and it's free. I guess, like me, ET members here tend to use the Testing or Unstable versions rather than the Stable one so you may not have seen it yourselves.Īny thoughts on what can we can do to help these users? One of the more experienced users reports that this happens sometimes but not always.And the filename is of the form AppData\Local\Temp\tmpABCD.tmp where ABCD is a hexadecimal number.The only common element is that these are all Stable 1.The stack trace is at RunActivity\Viewer3D\Materials.cs:line 142 in 4/5 cases and line 152 in the other.The routes include Microsoft JAPAN1 and Demo Model 1, so nothing odd there.The OS is both Windows 7 and Windows 10, both 32-bit and 64-bit, both Home and Pro.I've collected log files but it's difficult to see a common pattern. We're now up to 5 reported cases since mid-May (no doubt many more unreported). I reported 3 cases in an earlier thread and received useful advice - thanks, guys.
0 kommentar(er)
