System Information
Microsoft Windows 7 32-bit
4 GB RAM
NVidia GeForce 580 Ti
Blender Version
Broken: Blender 2.69.0 r60995
Crashes with previous stable version (2.68) too.
Short description of error
Every second time I try to render the scene, Blender crashes.
Exact steps for others to reproduce the error
Open the attached Blender scene. Render it, then render it again. The second time you are trying to render the scene, Blender crashes.
Since I have trouble to upload the files to this report in Opera, download the .blend file from here:
http://www.spook.freshsite.pl/Temporary/Blender/Polo10.blend
This error is not easy to repeat. Sometimes Blender renders the scene correctly a few times and then then crashes.
I've tapped into the Blender with Visual Studio and cought the exception. The details follows:
Output
(Starting rendering)
blender.exe has triggered a breakpoint.
The thread 0x15ac has exited with code 0 (0x0).
First-chance exception at 0x0072565B in blender.exe: 0xC0000005: Access violation writing location 0x00000040.
Unhandled exception at 0x0072565B in blender.exe: 0xC0000005: Access violation writing location 0x00000040.
Call stack:
blender.exe!0072565b() Unknown
[Frames below may be incorrect and/or missing, no symbols loaded for blender.exe] blender.exe!006fa056() Unknown blender.exe!006fa17a() Unknown blender.exe!006d6e48() Unknown blender.exe!006c70ef() Unknown blender.exe!006c754d() Unknown blender.exe!006c7832() Unknown blender.exe!006c7b62() Unknown blender.exe!006c7eb2() Unknown Pen_Tablet.dll!0aad18ae() Unknown Pen_Tablet.dll!0aaca26c() Unknown [External Code] blender.exe!0051fe86() Unknown blender.exe!0041a21d() Unknown pthreadVC2.dll!003d1e05() Unknown [External Code]
Minidump with heap
I've saved the minidump file from the crash. You can access it here:
http://www.spook.freshsite.pl/Temporary/Blender/blender.dmp (It should be available ~30 mins from posting this report, weighs around 700 Mb).
If you provide me with the debugging symbols for the stable version (Blender 2.69.0 r60995), I may try to post the resolved call stack.