Creating tmp. memory table kills the server

Version: 5.5.36-tokudb-7.1.5-MariaDB-log
Don't know if that's the right bugtracker to submit it, as now we're trying mariadb with toku enabled.

It seems that's data or structure dependent, if i do SELECT `domain` instead of `id` it won't crash. Also when i switch to other table, and do SELECT `id` it won't crash.

Table:

CREATE TABLE `raw_stats_lookup` (

  `id` int(11) NOT NULL AUTO_INCREMENT,

  `network_id` tinyint(11) NOT NULL,

  `creative_id` int(11) NOT NULL,

  `domain` varchar(90) NOT NULL,

  `__last_used` date NOT NULL,

  PRIMARY KEY (`id`),

  UNIQUE KEY `_uk` (`domain`,`network_id`,`creative_id`) USING BTREE,

  KEY `creative_id` (`creative_id`)

) ENGINE=Aria AUTO_INCREMENT=763772 DEFAULT CHARSET=utf8 PAGE_CHECKSUM=0 TRANSACTIONAL=0;

After issuing this query the DB is killed

CREATE TEMPORARY TABLE ___tmp_raw_stats_lookup ENGINE=MEMORY

    SELECT id

    FROM `stats`.raw_stats_lookup

    WHERE domain = 'x.com'

I made some other steps:

• duplicated the table and switched the engine to innodb (crashing again)
• moved the table to another server (just the table, not all data), same hardware and settings (keeps crashing)
• changed the ENGINE=MEMORY to ENGINE=MYISAM => no crash
• moved the data to machine with normal mariadb (5.5.35-MariaDB-log) - it WONT crash

For DB dump please contact me on email if you like to see, sorry, there's some domain data so don't want to share in public. pslawek83 !a-t! o2.pl ... if you want to look into this (in dump it said to report errors to you).

Attaching dump...

BTW: We had problems with making mariadb with toku running on FC20, compilation error then we compiled using mysql_release (instead of Release) but we ended up with debug version. Anything you can suggest that's tested? (OS + compile? OS + binary?)

Thanks everyone as always