I have been using 2.6 for a few days now and the one thing I have noted is how often it crashes rendering out animations. It’s definately 2.6 - I reinstalled 2.59 and had no problems. 2.60 halts with an attemped illegal memory access in most cases.
Has anyone else encountered this? It makes 2.6 pretty unusable in its current state.
I’ve also noticed it is a lot slower to render with the internal renderer (e.g. of recent render: 58 seconds for 2.59 and 1 minute 25 seconds for 2.60a)
Haven’t had any issues with crashing in 2.6, but I had an issue, 2.6 files would crash if I rendered in 2.59. Very repeatable. If I saved in 2.59, it rendered, but if I saved in 2.6, then ported over to my render computer, which I was lazy and didn’t upgrade immediately, until it crashed. Then I upgraded. No problems.
Yes I’ve noticed Blender will crash approximately 1 out of every 25 times I hit the render animation button.
Its very disappointing to hear of worse experience with 2.60 than 2.59 since we worked so hard to make it more stable.
but the complaints above have nowhere near enough info for anyone to look into the problems to find out a possible fix.
please file reports on the bug tracker (Help -> Report a Bug)
hey ideas man, may i say one here? it seems there might be a possible bug in the edit mode. First create a plane, then move it so you can add a mirror modifier, then hit alt+r and it will create an odd half circle between the planes (also you have to add a mirror modifier right before you do alt r
Haven’t had any issues with crashing in 2.6, but I had an issue, 2.6 files would crash if I rendered in 2.59. Very repeatable. If I saved in 2.59, it rendered, but if I saved in 2.6, then ported over to my render computer, which I was lazy and didn’t upgrade immediately, until it crashed. Then I upgraded. No problems
Hi, please report such bugs to the tracker. You really can’t expect developers to constantly search forums to fish out bugs. Bug tracker is the most convenient, centralised and fast way for developers to find the bug. Plus giving a test file to reproduce the problem makes it easier by far to fix the bug because they can pinpoint it better. A comment such as “render is buggy” means the developer will have to search through the entire render code to find mistakes. Not good, even for programmers.
For any one more interested this is a very nice article why this works:
There is a period before release where developers especially focus on the tracker for reports. It is not ignored. I realise most users despise having to go through this procedure but really it takes no longer than writing such a rant.
*Developers -do- care about bugs.
*If you care about it in the positive sense, make it easier for them, and yourself, and do post a bug report so that they find out about it.
Provide test files and use cases which reproduce the bug. -After- being ignored do rant about it 
*For really desperate people, the source code is open and you can get involved :p. OK this is a joke but true nonetheless.
Evil Moon MOose,This is simply the spin operator, not a bug 
haha, I was about to write basically what Psy-Fi is saying — sometimes its late and I want to look into the bug the next day… or I need some more information - an image, an example blend etc… forums are not good for this, if the bug is for another developer should I send him a personal mail linking to the forum — can you see how quickly this would become unmanageable?.
Bottom line.
Blender foundation employs devs to fix bugs in our tracker, other volunteer devs look there for bugs to fix too.
Reporting problems there is really the best way to help them get fixed.
Well, if you guys are referring to my issue (trying to render a 2.6 file using 2.59 cuases render crash) I upgraded all machines to 2.6. Problem fixed. Perhaps I’d be curious to know why, but I don’t have an issue now, so I don’t think it’s worth a bug track. And you’d be fixing 2.59 anyway.
Ahem.
Thanks for the feedback and I do appreciate that you devs want to get this right (I’m a dev too, so I know this).
I just wanted to know if anyone else had this memory problem before making a bug report. This isn’t a bug report per se!
I also need to have an example - sending you the animation I’m currently working on is probably not a good idea if I can find something more succinct.