D|S 4.7 Sometimes Crashes Unexpectedly When Rendering
I'm still using version 4.7, the final build before 4.8. After posing, etc., I sometimes can get a render to complete. At other times, D|S will crash. Sometimes, if I shut down the computer, wait awhile, and restart, things will be OK, and the render will complete. At other times, like today, nope, nothing works. I've been working with the same two figures in various poses, for awhile, the same setting, the same lights, the same render settings, so I don't have a clue as to why D|S will sometimes render and sometimes not.
Is there some significant flaw in the new file? (I always save the whole scene with a new name if I am going to do new poses.) I don't think so. Here's what I did today. After the crashes, several of them, I again, saved the new scene, with the add-on title "For Reality." So, yes, I tried Reality and Lux. The scene that I could not get to render in D|S is rendering fine in Lux. I did not tinker with Reality in the previous file. It just crashed, and that had nothing to do with Reality or Lux. I only tried Reality in the file after reserving the file with the add-on title.
I"m not trying to criticize D|S or anything like that. I'm just trying to figure out what's going on and if there's anything I could do that would quickly correct the problem and allow me to render in D|S. (Lux does take longer.) I'm not highly knowledgable about computer terminology, so trying to analyze the log file won't get me anywhere. I have earlier filed a bug report about this.
Oh, I should probably add that I'm on a Macintosh Pro running Yosemite 10.10.3.
Anyone have any suggestions?
Comments
Which rendering engine are you using? 3Delight or iRay?
If Iray are you using CPU or GPU rendering? Which model MP do you have, the line comes with a litany of GPU's, which one do you have?
How much RAM is in your system?
I'm still on 4.7, as it says above. The AMD cards on a Macintosh do not use CUDA or Iray. This has nothing to do with version 4.8 or Iray attempted rendering.
But ATI cards on the mac use OpenCL and OpenCL is apparently flawed in OS 10.10
While the card itself is not being used in rendering it is updating the display, there is an off chance but it's not definite.
Are you the admin? (if you have one account on your computer you are)
Have you run a permissions repair?
Have you tried a different admin account? (you can create multiple accounts, your primary account could be corrupt)
Is your runtime on an external drive or is it internal?
are you running Anti-Virus? (turn it off, better yet uninstall it, it's a waste of time on mac and a host of problems)
Is there a common item in the "sometimes crashes" category you overlooked? If so can you remove and test?
if you want to post a console crash log I can try and make heads or tails of it.
But ATI cards on the mac use OpenCL and OpenCL is apparently flawed in OS 10.10
Right. I believe they're working on a fix.
While the card itself is not being used in rendering it is updating the display, there is an off chance but it's not definite.
An off chance the CUDA would work?
Are you the admin? (if you have one account on your computer you are)
Yes, admin.
Have you run a permissions repair?
Yep, check my drives out all the time.
Have you tried a different admin account? (you can create multiple accounts, your primary account could be corrupt)
Don't think that's it. If I render in Reality and Lux, the file works fine.
Is your runtime on an external drive or is it internal?
Internal.
are you running Anti-Virus? (turn it off, better yet uninstall it, it's a waste of time on mac and a host of problems)
No. it's off.
Is there a common item in the "sometimes crashes" category you overlooked? If so can you remove and test?
Just that I spend a lot of time doing my own poses, often adjusting small positionings one way and then the other.
if you want to post a console crash log I can try and make heads or tails of it.
Well, back on April 21, I filed a bug report and submitted a log file. Would not allow me to attach the log file, but it has been submitted to the bug report people.
Since the problem seems to be intermittent, one thing you might do while waiting on the results of your support ticket is to run a memory test. Download a copy of Memtest 86+ in ISO format and use it to create bootable media. Then with the media inserted and your BIOS settings set to boot from the removable device, restart the machine and let Memtest run. It will take awhile, but at a minimum it should run for a complete pass of all tests. If no errors are reported you can usually assume that the memory is functioning as it should. If any errors are reported, you may have a hardware problem.