Comment 5 for bug 676945

Thanks for the additional information!

Actually, MariaDB 5.2.3 is now release as stable. So it should be fine to use.

Of course, it should be fixed in MariaDB 5.1 also. However, 5.1.39 is quite old by now, and it seems likely that if there is a fix for this in 5.2, the fix might also be in the latest 5.1 (5.1.51). So we would need to know if the bug is reproducable in 5.1.51 also or not.

If it is in 5.1.51, we should try to get a backtrace some way, or otherwise get more information to understand what the underlying problem is.