Actually I found why the error was happening and it was a legitimate bug and I found out exactly what caused it(it was much more complex then what I have reported). I have not tested it in the recent versions yet. But thanks for reminding me about this. I will check it in 4.4.3 and let you know.