Problem in Blender 2.71 Cycle Rendering Engine, system error “A problem caused the program to stop working correctly” Inbox x #42983

New Issue

Antonis Ryakiotakis · 2014-12-22T09:26:52+01:00

rajit.k commented

2014-12-22 09:26:52 +01:00

(Migrated from localhost:3001)

Processor: Intel(R) Xeon(R) CPU E5-2608 v2 @ 2.80GHz 2.80 GHz (Single Processor)
Installed memory (RAM) : 32 GB
System type : 64-bit Windows 8 Operating System, x64-based processor

Graphics Cards : NVIDIA Quadro K4000 and NVIDIA Tesla K20c
Blender Version 2.71
Broken: Date : 2014-06-25 18:36 Hash : 9337574
Worked: (optional)

Blender crashes after rendering about 220 frames ( where the entire frame range is 900 ) every time whenever I try with Cycle Render Engine with an error "A problem caused the program to stop working correctly”

My Blender file is consisting of 2 Simple Particle System with simple sphere instanced and 2 animated ( Simple Rotation Animation ) Torus Geometry with Displacement Modifier applied on to each of them along with a Cloud Shading network applied . The file also has a Sun Light . Now, while rendering these 2 animated Torus objects with Cycle Rendering Engine the crashing of Blender happens but, both the particles got rendered for the entire range of 900 frames. Even, when I was trying to start rendering these Torus Geometry after the number of frame it got rendered, the same crashing problem happened. This is also important to notice that I am using CPU based Cycle Rendering as the Shading network I made requires CPU based rendering otherwise using GPU Based Rendering would give me a bad black silhouette type output.

I am sorry, I could not be able to send the file as it is of 1.8 Gb which is not getting uploaded hens I am sending some snapshots of the options I used. Plz. tell me if you have any other way to send the .blend file to you for the check up.

Processor: Intel(R) Xeon(R) CPU E5-2608 v2 @ 2.80GHz 2.80 GHz (Single Processor) Installed memory (RAM) : 32 GB System type : 64-bit Windows 8 Operating System, x64-based processor Graphics Cards : NVIDIA Quadro K4000 and NVIDIA Tesla K20c Blender Version 2.71 Broken: Date : 2014-06-25 18:36 Hash : 9337574 Worked: (optional) Blender crashes after rendering about 220 frames ( where the entire frame range is 900 ) every time whenever I try with Cycle Render Engine with an error "A problem caused the program to stop working correctly” My Blender file is consisting of 2 Simple Particle System with simple sphere instanced and 2 animated ( Simple Rotation Animation ) Torus Geometry with Displacement Modifier applied on to each of them along with a Cloud Shading network applied . The file also has a Sun Light . Now, while rendering these 2 animated Torus objects with Cycle Rendering Engine the crashing of Blender happens but, both the particles got rendered for the entire range of 900 frames. Even, when I was trying to start rendering these Torus Geometry after the number of frame it got rendered, the same crashing problem happened. This is also important to notice that I am using CPU based Cycle Rendering as the Shading network I made requires CPU based rendering otherwise using GPU Based Rendering would give me a bad black silhouette type output. I am sorry, I could not be able to send the file as it is of 1.8 Gb which is not getting uploaded hens I am sending some snapshots of the options I used. Plz. tell me if you have any other way to send the .blend file to you for the check up. ![s_7.jpg](https://archive.blender.org/developer/F133107/s_7.jpg) ![s_4.jpg](https://archive.blender.org/developer/F133108/s_4.jpg) ![s_9.jpg](https://archive.blender.org/developer/F133109/s_9.jpg) ![s_8.jpg](https://archive.blender.org/developer/F133110/s_8.jpg) ![s_5.jpg](https://archive.blender.org/developer/F133111/s_5.jpg) ![s_6.jpg](https://archive.blender.org/developer/F133112/s_6.jpg) ![s_1.jpg](https://archive.blender.org/developer/F133113/s_1.jpg) ![s_2.jpg](https://archive.blender.org/developer/F133118/s_2.jpg) ![s_3.jpg](https://archive.blender.org/developer/F133121/s_3.jpg)

rajit.k commented

2014-12-22 09:26:52 +01:00

(Migrated from localhost:3001)

Changed status to: 'Open'

Antonis Ryakiotakis was assigned by blender-admin

2014-12-22 09:26:52 +01:00

rajit.k commented

2014-12-22 09:26:52 +01:00

(Migrated from localhost:3001)

Added subscriber: @rajit.k

blender-admin commented

2014-12-22 09:26:52 +01:00

#42957 was marked as duplicate of this issue

Sergey Sharybin commented

2014-12-22 10:08:13 +01:00

Added subscriber: @Sergey

Sergey Sharybin commented

2014-12-22 10:08:13 +01:00

You can send the file to ftp://download.blender.org/incoming/

However, there are some questions and suggestions to try:

Does crash always happen at the same exact frame?
if so, does rendering that single frame crash?
it is actually most likely threading conflict between viewport and render threads. So try setting Display to Fullscreen in the Render panel. You can also enable locked interface (a button with the lock next to Display in the same panel) just to be ensure there's no threading conflicts.
If previous one doesn't help, does the crash happen when rendering from the command like: blender.exe -b path\to\file.blend -a

You can send the file to ftp://download.blender.org/incoming/ However, there are some questions and suggestions to try: - Does crash always happen at the same exact frame? - if so, does rendering that single frame crash? - it is actually most likely threading conflict between viewport and render threads. So try setting Display to Fullscreen in the Render panel. You can also enable locked interface (a button with the lock next to Display in the same panel) just to be ensure there's no threading conflicts. - If previous one doesn't help, does the crash happen when rendering from the command like: blender.exe -b path\to\file.blend -a

Bastien Montagne commented

2014-12-22 10:14:24 +01:00

Added subscriber: @mont29

Bastien Montagne commented

2014-12-22 10:14:24 +01:00

First of all, please do not assign bugs yourself, and please test with latest builds form our buildbot, bug reports about a release that is already 6 months old are for sure not valid.

Also, such crash after such long render time on such big file could be caused by pretty much everything, blender, OS, drivers, hardware… Unless you can provide us a simple, reproducible case to investigate, including a .blend file, I'm afraid we can't do much here.

First of all, please do not assign bugs yourself, and please test with latest builds form [our buildbot](https://builder.blender.org/download), bug reports about a release that is already 6 months old are for sure not valid. Also, such crash after such long render time on such big file could be caused by pretty much everything, blender, OS, drivers, hardware… Unless you can provide us a simple, reproducible case to investigate, including a .blend file, I'm afraid we can't do much here.

Antonis Ryakiotakis was unassigned by Bastien Montagne

2014-12-22 10:17:19 +01:00

Antonis Ryakiotakis commented

2014-12-22 10:33:18 +01:00

Added subscribers: @Psy-Fi, @JulianEisel

Antonis Ryakiotakis commented

2014-12-22 10:46:35 +01:00

This looks like a simple setup and the only thing that is causing the file size to explode is the particle amount. You could just lower the amount of particles as needed to make the file smaller, save the file and upload this version, then just mention the amount of particles that it should normally have.
I expect the crash should be there with a lower amount of particles too, but to me this sounds a bit like an out of memory issue. We'll see though.

This looks like a simple setup and the only thing that is causing the file size to explode is the particle amount. You could just lower the amount of particles as needed to make the file smaller, save the file and upload this version, then just mention the amount of particles that it should normally have. I expect the crash should be there with a lower amount of particles too, but to me this sounds a bit like an out of memory issue. We'll see though.

rajit.k commented

2014-12-22 13:52:39 +01:00

(Migrated from localhost:3001)

Ya. the crash always happen at the same exact frame i.e. 220 and whenever I am trying to start rendering it again from 221 it crashes. Actually, I am not rendering through any command rather I am doing so by clicking on Animation button under Render rollout.

Well, I am sending the file as I could reduce down the file size by decreasing the amount of particle as psy-fi (Antony Riakiotakis) suggested me. My actual particle amount was 5000 for each of the Particle Emitter.

Could you plz. suggest me the maximum limit of file upload as I have reduced the file size to around 10 Mb and tried to upload it but, it is not uploaded as it says that the upload size is too big.

Ya. the crash always happen at the same exact frame i.e. 220 and whenever I am trying to start rendering it again from 221 it crashes. Actually, I am not rendering through any command rather I am doing so by clicking on Animation button under Render rollout. Well, I am sending the file as I could reduce down the file size by decreasing the amount of particle as psy-fi (Antony Riakiotakis) suggested me. My actual particle amount was 5000 for each of the Particle Emitter. Could you plz. suggest me the maximum limit of file upload as I have reduced the file size to around 10 Mb and tried to upload it but, it is not uploaded as it says that the upload size is too big.

rajit.k commented

2014-12-22 13:58:29 +01:00

(Migrated from localhost:3001)

Plz. check the file now but it is a compressed file with 7z. Plz. extract the file and increase the amount of particle to 5000 for each of the emitter. plz. try rendering the Cloud Belt for 900 frames as the problem is only happening with the Cloud Belt which is a Displaced Torus. Moreover the 5000 count of particles have already been rendered.

Final_Particle_Smoke_Simulation_with_Bang_3_Particle_Simulation_Baked_1_Passes_Rendering_2_without_Bake_1.7z

Plz. check the file now but it is a compressed file with 7z. Plz. extract the file and increase the amount of particle to 5000 for each of the emitter. plz. try rendering the Cloud Belt for 900 frames as the problem is only happening with the Cloud Belt which is a Displaced Torus. Moreover the 5000 count of particles have already been rendered. [Final_Particle_Smoke_Simulation_with_Bang_3_Particle_Simulation_Baked_1_Passes_Rendering_2_without_Bake_1.7z](https://archive.blender.org/developer/F133136/Final_Particle_Smoke_Simulation_with_Bang_3_Particle_Simulation_Baked_1_Passes_Rendering_2_without_Bake_1.7z)

Sergey Sharybin commented

2014-12-22 14:13:17 +01:00

Is it possible to open the file, modify number of particles, go to specific frame, render and observe crash?

EDIT: I mean, without rendering 900 frames first.

Is it possible to open the file, modify number of particles, go to specific frame, render and observe crash? EDIT: I mean, without rendering 900 frames first.

Aaron Carlisle commented

2014-12-22 19:43:18 +01:00

Added subscriber: @Blendify

Aaron Carlisle commented

2014-12-22 20:19:56 +01:00

The file size limit is about five MB. If you have trouble with that dropbox and any other cloud is good to use

Sergey Sharybin commented

2014-12-22 20:25:16 +01:00

@Blendify, please leave triaging to the developers. "Incomplete" means reporter's action or information is required, "Normal" means all the information needed for fixing in there.

This issue we're not ready to solve at all, waiting 900 frames to render is not really a good use of developer's time. Bug fixing is 50% time of user to give easy-to-reproduce case and then developers can investigate what's wrong in the code and fix.

@Blendify, please leave triaging to the developers. "Incomplete" means reporter's action or information is required, "Normal" means all the information needed for fixing in there. This issue we're not ready to solve at all, waiting 900 frames to render is not really a good use of developer's time. Bug fixing is 50% time of user to give easy-to-reproduce case and then developers can investigate what's wrong in the code and fix.

Aaron Carlisle commented

2014-12-22 20:35:27 +01:00

I am sorry I did not see your latest question

Antonis Ryakiotakis commented

2014-12-22 22:16:57 +01:00

Can't reproduce on Windows 7 64bit with blender 2.72b (open file, change two particle emmiters to 5000, render on frame 221 seems fine).

Have you tried rendering the file on 2.72?

Can't reproduce on Windows 7 64bit with blender 2.72b (open file, change two particle emmiters to 5000, render on frame 221 seems fine). Have you tried rendering the file on 2.72?

rajit.k commented

2014-12-23 07:09:44 +01:00

(Migrated from localhost:3001)

Well, as you say the Rendering runs fine in Blender 2.72, I am going to try the same in this version and let you know whether it works or not. But, can you tell me the reason why the animated Torus with a simple Displacement Modifier applied creates a problem during Cycle Rendering where 5000 count of Particles got rendered properly for 900 frames. I actually want to know whether it is a Software Bug or it is any error in the process I am going through ?

Sergey Sharybin commented

2014-12-25 11:51:56 +01:00

@rajit.k, please also test 2.73rc1 from http://download.blender.org/release/Blender2.73/ There are some threading issues fixed in there.

And we can not tell you why your file crashes without being able t reproduce the crash. If it's animation rendering, then it's most likely a threading conflict between render and viewport thread, Solving this is not simple and it's in our TODO already. To work that around you might render with locked interface or in fullscreen as i suggested in my original reply to you.

@rajit.k, please also test 2.73rc1 from http://download.blender.org/release/Blender2.73/ There are some threading issues fixed in there. And we can not tell you why your file crashes without being able t reproduce the crash. If it's animation rendering, then it's most likely a threading conflict between render and viewport thread, Solving this is not simple and it's in our TODO already. To work that around you might render with locked interface or in fullscreen as i suggested in my original reply to you.

Julian Eisel commented

2015-01-02 14:10:20 +01:00

Changed status from 'Open' to: 'Archived'

Julian Eisel closed this issue

2015-01-02 14:10:20 +01:00

Julian Eisel self-assigned this 2015-01-02 14:10:20 +01:00

Julian Eisel commented

2015-01-02 14:10:20 +01:00

Closed for the following reasons:

We are still waiting on @rajit.k to test with the latest builds after almost two weeks
We are still waiting on @rajit.k to do all the other tests asked by @Sergey (also after almost two weeks)
We were still not able to reproduce (tried myself, no crash after 250 frames)

We have to be verry strict to keep our bug tracker organized, so please try to follow the instructions and answer the questions we give you, otherwise we won't be able to help you much. If you have the information we asked for, you did the tests we asked for and the crash still occurs (should also be reproducible), we can reopen.

Closed for the following reasons: * We are still waiting on @rajit.k to test with the latest builds after almost two weeks * We are still waiting on @rajit.k to do all the other tests asked by @Sergey (also after almost two weeks) * We were still not able to reproduce (tried myself, no crash after 250 frames) We have to be verry strict to keep our bug tracker organized, so please try to follow the instructions and answer the questions we give you, otherwise we won't be able to help you much. If you have the information we asked for, you did the tests we asked for and the crash still occurs (should also be reproducible), we can reopen.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Problem in Blender 2.71 Cycle Rendering Engine, system error “A problem caused the program to stop working correctly” Inbox x #42983