Hi,
The Alpha1 was crashing during several operations - most notably if I simply rendered the same scene twice in a row (easy to reproduce: F12, Esc to clear, F12 again. A few things prevent this such as moving the view slightly between renders). This is still happening in Alpha2. Is anyone else seeing this?
Thanks!
Don’t have any 2.5 with me right now, but it wouldn’t surprise me. Alpha2 was released because of 1 fixed bug concerning image textures, I believe.
Some time ago I noticed when you set the Render Display to ‘new window’, it reduces the amount of crashes when rendering greatly. Still doing that in Alpha2, works fine for me
Nice one! Works well. Thanks!
I’ve also found that clicking the render button, instead of using F12, seemed to reduce the number of crashes.
If you don’t use “Compositing”, than deactivate it under “Post Processing”. It will reduce crashes, too.
Thanks for the hint! That really helps. Crashes (I think due to thi glitch) were kinda buggin me. I actually save my scene before every render - something which I normally would not have developed 
I can consistently reproduce the bug. Do the following with the default scene.
Ira
To me is more easy is just matter of open Blender and render three times in a row, it crash always, even with a default cube, i overcome that using a build from graphicall, that works much better, but some times crash, and yes if you render in a new window the crashes reduce greatly.
It could NOT be a problem in the render engine because the crashes are consistent when i am using other external render engine, for example i use the SmallLuxGPU render with the python exporter and blender crashes too in the same way after hit F12.
To me, it looks like one of the following:
a memory leak, where the render engine doesn’t give back all the memory back to Blender when the render engine is finished (i.e., the return which is executed when you hit Esc after rendering), or:
an object reference that is not freed when the render engine returns, so that the program goes to an area in memory that it shouldn’t go to.
These are very common problems in C++.
I should mention that I’m running Blender on 32 bit Windows Vista. A member of my forum tried it on Linux and did not have this problem. Perhaps the problem is OS specific.
irakrakow-- try changing the default render display to ‘New Window’ or ‘Image Editor’ instead of ‘Full Screen.’ That fixed it here in XP 32-bit-- doesn’t crash anymore; can render as many times as I want.
Only problem is when hitting ESC to close a new render window, it doesn’t go back to the main Blender window automatically – keeps the render window selected, but in the background. If I click the ‘close window X’ then it does keep Blender’s main window in focus though.
I have found that the 64 bit builds don’t seem to crash either
pixelmans solution seems to work as well
Blender 2.5 crashes when I press 12 more than 2 or 3 times, consistently. It has been this way for a long time. Seems strange that this bug is not the top of the “to fix” list.
In the meantime i’ll use the suggestions on here to work around the problem until fixed.
man , is alpha software.
And released to find bugs and comment about them.
I had a crash here on alpha 2 when I subdivided base cube, smoothed, added subsurf, then pressed F12. Crash. I will try the other tips you mentioned here.
The main thing, as with all software development, is to fix fatal crashes first. If you’re trying to get feedback on your features, the last thing you need is it crashing so that we can’t even explore the features! It may be that there are a lot of these fatal errors and they’re being tackled diligently by the devs. This is a big, complex project and the work so far is outstanding!
However, if someone, somewhere is working on fixing typos and/or getting their panel layouts just right, they need to redirect their attention 
I think I know the source of this particular oversight. First, it looks like the problem is related to 32 bit Windows versions. I’m sure the developers all have the latest and greatest 64 bit machines and are running, for the most part, in Linux. If they run in Windows it would be the 64 bit Windows version, most probably on Windows 7.
A significant part of the user base, however, runs in 32 bit Windows, either XP or Vista. The developers will run their test suite, which will run fine. It’s only when they release to a wider user base, such as putting it on blender.org, will this problem surface.
The solution is to report the problems on the official Blender.org bug tracking system, at:
http://www.blender.org/development/report-a-bug/
Once the developers see the problems, I’m sure they will address them on Win32 as well.
Hi all, if any of you do your own builds of blender, you can do a debug build, then when you get a crash do a backtrace and provide the backtrace and put it in the bug tracker. Saves time for developers and gets your bug fixed quicker.
LetterRip