Bug #6406 DISTINCT + SUBQUERY + ORDER BY crashes server

Description:
This bug looks very similar to #6303, but #6303 didn't crash under 4.1.8 

How to repeat:
4.1.8-debug-log 
[18:02] root@test> create table t1 (a int, b int); 
Query OK, 0 rows affected (0.10 sec) 
 
4.1.8-debug-log 
[18:02] root@test> create table t2 (a int, b int); 
Query OK, 0 rows affected (0.12 sec) 
 
4.1.8-debug-log 
[18:02] root@test> insert into t1 values (1,1),(1,2),(1,3),(2,4),(2,5); 
Query OK, 5 rows affected (0.03 sec) 
Records: 5  Duplicates: 0  Warnings: 0 
 
4.1.8-debug-log 
[18:02] root@test> insert into t2 values (1,3),(2,1); 
Query OK, 2 rows affected (0.03 sec) 
Records: 2  Duplicates: 0  Warnings: 0 
 
4.1.8-debug-log 
[18:02] root@test> select distinct a,b, (select max(b) from t2 where t1.b=t2.a) from 
t1 order by t1.b; 
ERROR 2013 (HY000): Lost connection to MySQL server during query 
4.1.8-debug-log 
[18:02] root@test> 

Suggested fix:

Verified on latest BK source 5.0

ChangeSet 
  1.2107 04/11/16 00:16:04 bell@sanja.is.com.ua +4 -0 
  fixed joincleunup to avoid double deletin tables, and too earlyfull cleanup in case of 
EXPLAIN 
  fixed cleunup of TMP_TABLE_PARAM 
  (BUG#6406)

Thank you for bugreport, Bug is fixed and patch is pushed to our source repository.