Hi，
We use cc to do reconstruction. But a lot of tasks got stuck for a long time. For example, it takes about 5 hours to complete a task, However, the stuck task has been in a running status for over 10 hours. We use procmon to monitor the CCTask.exe and find no messages for these stuck tasks. We also found that a few of tasks failed due to insufficient memory during Photos pairwise matching.
We rerun the stuck tasks and use procmon to monitor the messges of CCtask.exe process. Then we find that the CCtask.exe will write a lot of logs before getting stuck. so we grap the log file when it starts to write a lot of logs suddenly. Please help us to analyze the log file. Why does it write a lot of logs? What should we do next? Thank you very much!
task_log_0 .log
Hi kh,
Looking at your log, it seems one cache file is corrupted (cache\44\8148BBA10E3CA728EB113ED631863BFE4F36B8ED6753B50BFCDA0611FA5913.a3d located in your project files). It then corrupts the log, so I can't see what's happening. I recommend deleting this cache file. Are you working with network drives, or is everything done on a local computer?
- Cyril
Hi, Thank you very much! We use network drives in this project. Why is the probability of corruption of files in cache and image directory so high?
All our QA is done using network drives, and devs are regularly using network drives for their testing. I suspect there's an issue or a high latency in your setup that may cause these issues. Do you also have enough disk space?
We use the cc with version 4.4.14.60. This version will set the cache directory in the TEMP directory. We use a SSD disk as our system drive. The project directory of the project is set in a network drive. The system drive and the network drive all have enough disk space.