Hey gang!
I’m finishing up my newest animated short (a tasty Cycles render - my FIRST!:evilgrin:) and I’m having a NASTY crash in the sequencer.
I have the Fastest 2.59 Graphicall revision 39401 by Alb.
I just have the image sequence and a music track, set to AVsync.
Everything’s fine for a while, but I’m a perfectionist when it comes to syncing vid to Just The Right Beat, so shifting the audio around works great for a while then CRASH!
I’ve tried hitting the “refresh sequencer” button when I get things close or anytime I move something, but still the same deal…
Anyone have a quick fix, or should I go to Graphicall and post a comment on Alb’s build? I don’t even have a Graphicall account…
Or is this something we should submit as a bug to Blender Organization itself? I’ve never done anything like that before and I know those guys work overly hard. I don’t want to bug them if there’s just something I’m doing obviously wrong, or if it’s just something squirrely in Alb’s build. Campbell Barton posted some notes in there that there were recent sequencer fixes to this particular build, so… 
Hi there! I know the 2.59 is announced to be “stable”… but it crashes…
But he is not using a stable version, he is using a development build from graphicall. If you find a bug just use the bug report link in the blender help menu.
On a fair note, the offical 2.59 is shaky on it´s legs like a newborn giraffe.
I use 2.58 and 2.59 official and both seem to leak memory like hell or have huge problems with malloc and realloc.
Whenever you work with big textures, the sequencer, move objects between layers or undo computational intensive operations they just crash. And it´s no reproduceable bug you could report. It´s simply unstable like hell.