Crash #44983

New Issue

Patrick Anderson · 2015-06-07T00:19:03+02:00

Patrick Anderson commented

2015-06-07 00:19:03 +02:00

System Information
Operating system and graphics card
8 GB ram
windows 8.0
Intel(R) HD graphics (I use blender through intel graphics so it might be opengl problem but render on gpu with nvidia)
Opengl version 4.0.0 (NO UPDATE)
Blender Version
Broken: 2.74 4aa5109
Worked: (optional)

Short description of error
Assume you're rendering a scene that need lot of time to finish on your laptop, you must close the lid after then. You open lid latter and try to see finished results... Everything got dumped in the trash and appears to be a crash, kinda poetry or something BUT IT'S VERY DISAPPOINTING to wait hours and then get a crash.
Exact steps for others to reproduce the error
Render a scene that takes at least 2400 MB of RAM and about hour to finish and close laptop lid, then open and blender will crash.

**System Information** Operating system and graphics card 8 GB ram windows 8.0 Intel(R) HD graphics (I use blender through intel graphics so it might be opengl problem but render on gpu with nvidia) Opengl version 4.0.0 (NO UPDATE) **Blender Version** Broken: 2.74 4aa5109 Worked: (optional) **Short description of error** Assume you're rendering a scene that need lot of time to finish on your laptop, you must close the lid after then. You open lid latter and try to see finished results... Everything got dumped in the trash and appears to be a crash, kinda poetry or something BUT IT'S VERY DISAPPOINTING to wait hours and then get a crash. **Exact steps for others to reproduce the error** Render a scene that takes at least 2400 MB of RAM and about hour to finish and close laptop lid, then open and blender will crash.

Patrick Anderson commented

2015-06-07 00:19:03 +02:00

Changed status to: 'Open'

Patrick Anderson commented

2015-06-07 00:19:03 +02:00

Added subscriber: @Stalk1500

Bastien Montagne commented

2015-06-07 09:40:48 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2015-06-07 09:40:48 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2015-06-07 09:40:48 +02:00

Bastien Montagne self-assigned this 2015-06-07 09:40:48 +02:00

Bastien Montagne commented

2015-06-07 09:40:48 +02:00

You must deactivate the sleep mode of your computer (or at least, it’s triggering by lid closing). GPU rendering does not support this at all, so thanks for the report, but not a Blender bug at all.

Patrick Anderson commented

2015-06-07 11:11:26 +02:00

Nope, take a look:

The issue isn't from sleep mode but turning off the display since when lid is closed display is turned off no matter how much time to wait in order to open it again blender crash.
Plus I don't have a sleep button.

Nope, take a look: ![vfcxbewftrf.png](https://archive.blender.org/developer/F186711/vfcxbewftrf.png) ![fvsdvbxcf.png](https://archive.blender.org/developer/F186715/fvsdvbxcf.png) The issue isn't from sleep mode but turning off the display since when lid is closed display is turned off no matter how much time to wait in order to open it again blender crash. Plus I don't have a sleep button.

Bastien Montagne commented

2015-06-07 11:18:37 +02:00

Changed status from 'Archived' to: 'Open'

Bastien Montagne reopened this issue

2015-06-07 11:18:37 +02:00

Bastien Montagne commented

2015-06-07 11:18:37 +02:00

Well, in this case we need the .blend file that crashes. Also:

Do you get any message before crash (run blender from a commandline, so that it does not disappear in case of crash)?
Does it crash when you do not close the lid?
Do you always get that crash when closing the lid?
Do you get crash when rendering a very simple scene (taking just enough time to render for you to close the lid)?

Also, stuff like that does not help anyone to investigate the issue:

Everything got dumped in the trash and appears to be a crash, kinda poetry or something BUT IT'S VERY DISAPPOINTING to wait hours and then get a crash.

Please give specific, useful and precise info.

Well, in this case we need the .blend file that crashes. Also: * Do you get any message before crash (run blender from a commandline, so that it does not disappear in case of crash)? * Does it crash when you do not close the lid? * Do you *always* get that crash when closing the lid? * Do you get crash when rendering a very simple scene (taking just enough time to render for you to close the lid)? Also, stuff like that does not help anyone to investigate the issue: > Everything got dumped in the trash and appears to be a crash, kinda poetry or something BUT IT'S VERY DISAPPOINTING to wait hours and then get a crash. Please give specific, useful and precise info.

Patrick Anderson commented

2015-06-07 12:28:27 +02:00

My fault then, sorry.
Can you tell me how to run blender from commandline?
I've tried to launch it from there by typing start work1.blend and it opened but in cmd it just made a space and new command.
I don't remember it happened to crash when I don't close the lid and the crash happens when rendering heavy load.
It doesn't crash in simple scene.

It will take time to reproduce the crash since first it will need time to render, second i will render it many times at different sets to narrow the edge of taking random possibilities also I want to know how running blender through cmd goes.

My fault then, sorry. Can you tell me how to run blender from commandline? I've tried to launch it from there by typing start work1.blend and it opened but in cmd it just made a space and new command. I don't remember it happened to crash when I don't close the lid and the crash happens when rendering heavy load. It doesn't crash in simple scene. It will take time to reproduce the crash since first it will need time to render, second i will render it many times at different sets to narrow the edge of taking random possibilities also I want to know how running blender through cmd goes.

Bastien Montagne commented

2015-06-07 12:53:51 +02:00

Regarding commandline, this post should help you: http://blender.stackexchange.com/questions/21772/how-to-view-the-system-console-message-after-blender-crashes

Also, are you sure this was not an hardware failure (due to overheating)? Depending on laptop, closing lid can increase heat (due to part of it 'leaking' from keyboard area and such…). And one hour GPU rendering is rather intense task for a laptop in any case.

Regarding commandline, this post should help you: http://blender.stackexchange.com/questions/21772/how-to-view-the-system-console-message-after-blender-crashes Also, are you sure this was not an hardware failure (due to overheating)? Depending on laptop, closing lid can increase heat (due to part of it 'leaking' from keyboard area and such…). And one hour GPU rendering is rather intense task for a laptop in any case.

Patrick Anderson commented

2015-06-07 16:51:19 +02:00

Now I have set cmd to act as blender console window; it's working well.
We will need to wait a couple of days at maximum to get the crash happen again. I can't specify whether it's a hardware failure or not cause there's no sign for this and more than that the laptop is always fixed on cooler when rendering so probably it's not the case.

Now I have set cmd to act as blender console window; it's working well. We will need to wait a couple of days at maximum to get the crash happen again. I can't specify whether it's a hardware failure or not cause there's no sign for this and more than that the laptop is always fixed on cooler when rendering so probably it's not the case.

Patrick Anderson commented

2015-06-07 17:05:15 +02:00

Okay just now blender crashed when closed lid and opened and maximized blender after being minimized straight on taskbar, this was the last output of blender before exiting:

Error: EXCEPTION_ACCESS_VIOLATION
Writing: C:\Users\HP\AppData\Local\Temp\work1.crash.txt

The work1.crash.txt file:
work1.crash.txt

For note, the scene took 3 hours to render and didn't crashed but when i re-render it again it crashed while still doing the first tile of 45, too I've changed the tiles size from 256 to 512.

Okay just now blender crashed when closed lid and opened and maximized blender after being minimized straight on taskbar, this was the last output of blender before exiting: Error: EXCEPTION_ACCESS_VIOLATION Writing: C:\Users\HP\AppData\Local\Temp\work1.crash.txt The work1.crash.txt file: [work1.crash.txt](https://archive.blender.org/developer/F186938/work1.crash.txt) For note, the scene took 3 hours to render and didn't crashed but when i re-render it again it crashed while still doing the first tile of 45, too I've changed the tiles size from 256 to 512.

Bastien Montagne commented

2015-06-08 16:16:50 +02:00

Unfortunately, crash reports with non-debug builds under Windows are unusable (they have been removed in upcomming 2.75) :/

Can you by any chance try your scenes on another computer, to see if it crashes there too? Problem is, in current state, this case is impossible to investigate for us (crashing with some unknown huge files after hours of rendering…).

Unfortunately, crash reports with non-debug builds under Windows are unusable (they have been removed in upcomming 2.75) :/ Can you by any chance try your scenes on another computer, to see if it crashes there too? Problem is, in current state, this case is impossible to investigate for us (crashing with some unknown huge files after hours of rendering…).

Bastien Montagne removed their assignment 2015-06-08 16:17:31 +02:00

Aaron Carlisle commented

2015-06-11 16:21:04 +02:00

Added subscriber: @Blendify

Aaron Carlisle commented

2015-06-11 16:21:04 +02:00

is there any chance we can have a .blend that crashes for you

Antonis Ryakiotakis commented

2015-06-11 16:40:33 +02:00

Added subscriber: @Psy-Fi

Antonis Ryakiotakis commented

2015-06-11 16:40:33 +02:00

Changed status from 'Open' to: 'Archived'

Antonis Ryakiotakis closed this issue

2015-06-11 16:40:33 +02:00

Antonis Ryakiotakis self-assigned this 2015-06-11 16:40:33 +02:00

Antonis Ryakiotakis commented

2015-06-11 16:40:33 +02:00

Hi, this is not a blender issue, the OpenGL context is lost completely when you close the lid and blender does not yet handle context losses robustly (would be quite a big TODO but currently it just does not work). If you want to render like that use a command line render, see http://www.blender.org/manual/render/workflows/command_line.html. We will be closing the issue now.

Patrick Anderson commented

2015-06-11 20:25:53 +02:00

Thanks for info! Rendering through cmd is much simpler and saving bit of ram too, I hope it will solve the lid problem.

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

Crash #44983