In this case, it does not. I have verified that innodb_use_sys_malloc=0 (or =1) works, but loose_innodb_use_sys_malloc=0 does not. It is a regression because loose_innodb_use_sys_malloc=0/1 works in 5.1, but does not work in 5.5. The bug may be in the server layer. Please...
The reason why Valgrind does not report this memory leak in InnoDB versions before the Plugin 1.0 is that they do not implement innodb_use_sys_malloc=1. That is, an attempt to re-CREATE an InnoDB table whose .frm file does not exist will leak memory. Valgrind will not complain, because...
I have just spoken to a friend whose DS is at the same school and she reassured me that lots of students (including her DS) drop their 4th subject before Christmas of Year 12, without any pushback, so I think we'll just go along with selecting four subjects, in the knowledge he can...
malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8384512 read_buffer_size=131072 max_used_connections=1 max_threads=151 threads...
Some analysis... Using mysql-next-mr, the output of: $ mysqlbinlog -v 38718/xp64-relay-bin.000002 ends up in Segmentation Fault. Apparently, this seems to be a corrupted relay log. How it got corrupted in the first place, I cannot tell (might even have been for any reason outside...