Blender crash #52165

New Issue

Matthew Dougherty · 2017-07-24T00:15:39+02:00

Matthew Dougherty commented

2017-07-24 00:15:39 +02:00

System Information
Two Mac Pros, current OS

Mac Pro (Late 2013)
3.7 GHz Quad-Core Intel Xeon E5
16 GB 1866 MHz DDR3
AMD FirePro D500 3072 MB

Mac Pro (Late 2013)
3.5 GHz 6-Core Intel Xeon E5
64 GB 1600 MHz DDR3 ECC
AMD FirePro D300 2048 MB

Blender Version
2.78
standard defaults, not experimental mode.

Short description of error
rendering the same blend file on two mac pro's, not connected as render farm, both are standalone.

the 64GB has consistently crashed after 200-1200 frames on several projects.
The 16GB has not crashed, ever.

not sure how to further analyze problem.

Exact steps for others to reproduce the error
unknown

**System Information** Two Mac Pros, current OS Mac Pro (Late 2013) 3.7 GHz Quad-Core Intel Xeon E5 16 GB 1866 MHz DDR3 AMD FirePro [D500](https://archive.blender.org/developer/D500) 3072 MB Mac Pro (Late 2013) 3.5 GHz 6-Core Intel Xeon E5 64 GB 1600 MHz DDR3 ECC AMD FirePro [D300](https://archive.blender.org/developer/D300) 2048 MB **Blender Version** 2.78 standard defaults, not experimental mode. **Short description of error** rendering the same blend file on two mac pro's, not connected as render farm, both are standalone. the 64GB has consistently crashed after 200-1200 frames on several projects. The 16GB has not crashed, ever. not sure how to further analyze problem. **Exact steps for others to reproduce the error** unknown

Matthew Dougherty commented

2017-07-24 00:15:39 +02:00

Changed status to: 'Open'

Matthew Dougherty commented

2017-07-24 00:15:39 +02:00

Added subscriber: @matthewd

Ray molenkamp commented

2017-07-24 00:34:27 +02:00

Added subscriber: @LazyDodo

Ray molenkamp commented

2017-07-24 00:34:27 +02:00

Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

A guideline for making a good bug report can be found here: https://wiki.blender.org/index.php/Dev:Doc/Process/Bug_Reports

Marking as "Incomplete" until the requested information/data is provided.

Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc. A guideline for making a good bug report can be found here: https://wiki.blender.org/index.php/Dev:Doc/Process/Bug_Reports Marking as "Incomplete" until the requested information/data is provided.

Matthew Dougherty commented

2017-07-24 00:50:30 +02:00

not sure how to proceed. Looked at bug reports URL. provided as much info as I have.

There is a good possibility it is a hardware ram problem, or some other intermittent hardware-meets-blender problem; not failing on other applications. On one crash it took out the OS.

Trying to get advice how to triage out blender bug as cause.

The blend file is over 500MB and seems to fail only on one machine. Doubt anyone is going to replicate problem, or be able to dig deeper as to cause except on the machine it is failing on.

Need advice on how to diagnose this to determine if it is really a blender problem.

not sure how to proceed. Looked at bug reports URL. provided as much info as I have. There is a good possibility it is a hardware ram problem, or some other intermittent hardware-meets-blender problem; not failing on other applications. On one crash it took out the OS. Trying to get advice how to triage out blender bug as cause. The blend file is over 500MB and seems to fail only on one machine. Doubt anyone is going to replicate problem, or be able to dig deeper as to cause except on the machine it is failing on. Need advice on how to diagnose this to determine if it is really a blender problem.

Brecht Van Lommel commented

2017-07-24 01:05:55 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2017-07-24 01:05:55 +02:00

Do you have a crash log that you can attach to this report? Two places to look:

In the Console application on macOS, under System Reports.
In the Finder, Go > Go To Folder ... > type "/tmp", there may be a crash log written by Blender.

I assume you are using Cycles for rendering, is that using the CPU or AMD GPU?

Do you have a crash log that you can attach to this report? Two places to look: * In the Console application on macOS, under System Reports. * In the Finder, Go > Go To Folder ... > type "/tmp", there may be a crash log written by Blender. I assume you are using Cycles for rendering, is that using the CPU or AMD GPU?

Matthew Dougherty commented

2017-07-24 01:16:00 +02:00

Using cycles, render is set for CPU.
I looked for the crash log in the folder of the blend file, nothing.
will look at the other locations, thanks.

referencing https://wiki.blender.org/index.php/Dev:Doc/Process/Bug_Reports
"However if the bug randomly happens without any clear steps leading up to it, then it is unlikely developers will be able to fix the bug."
I have feeling this is going end up here, being that a lesser machine can render without fail, and the superior machine fails.

Using cycles, render is set for CPU. I looked for the crash log in the folder of the blend file, nothing. will look at the other locations, thanks. referencing https://wiki.blender.org/index.php/Dev:Doc/Process/Bug_Reports "However if the bug randomly happens without any clear steps leading up to it, then it is unlikely developers will be able to fix the bug." I have feeling this is going end up here, being that a lesser machine can render without fail, and the superior machine fails.

Ray molenkamp commented

2017-07-24 02:16:39 +02:00

if you can share the .blend that is causing issues that might also help