Windows 2008 R2 64Bit

Hi,

Does the table contain confidential information? Would you be able to upload it (all three files .frm, MAI, MAD) to ftp.askmonty.org/private?

I just uploaded the files.

Any news regarding this ticket?

Thanks for the data. I was able to reproduce the problem.
Apparently, it only happens on Windows, and only on non-debug builds.

The culprit is aria_pagecache_buffer_size value.

RaphaelH, as a workaround, please try to reduce the value to something not bigger than 4G.

When it exceeds 4260M, bad things start happening.

• when it's greater than 4262M, the error happens upon select:

  mysql -uroot test -e "select * from t1" > t1.data

  ERROR 1030 (HY000) at line 1: Got error 22 "Invalid argument" from storage engine Aria

• when it's 4261M or 4262M, the server crashes upon the same select:

  Version: '10.0.24-MariaDB' socket: '' port: 3306 Source distribution

  160303 2:32:51 [ERROR] mysqld got exception 0xc0000005 ;

  This could be because you hit a bug. It is also possible that this binary

  or one of the libraries it was linked against is corrupt, improperly built,

  or misconfigured. This error can also be caused by malfunctioning hardware.

  To report this bug, see http://kb.askmonty.org/en/reporting-bugs

  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.

  Server version: 10.0.24-MariaDB

  key_buffer_size=134217728

  read_buffer_size=131072

  max_used_connections=1

  max_threads=501

  thread_count=0

  It is possible that mysqld could use up to

  key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1223927 K bytes of memory

  Hope that's ok; if not, decrease some variables in the equation.

  Thread pointer: 0x0x0

  Attempting backtrace. You can use the following information to find out

  where mysqld died. If you see no messages after this, something went

  terribly wrong...

  ntdll.dll!RtlDeNormalizeProcessParams()

  ntdll.dll!RtlDeNormalizeProcessParams()

  mysqld.exe!os_mutex_enter()[os0sync.cc:761]

  mysqld.exe!sync_array_wake_threads_if_sema_free_low()[sync0arr.cc:949]

  mysqld.exe!sync_arr_wake_threads_if_sema_free()[sync0arr.cc:989]

  mysqld.exe!srv_error_monitor_thread()[srv0srv.cc:2189]

  kernel32.dll!BaseThreadInitThunk()

  ntdll.dll!RtlUserThreadStart()

  The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains

  information that should help you find out what is causing the crash.

On some reason, I cannot reproduce it on MariaDB 10.1, only 5.5 and 10.0 are affected. Maybe it was fixed, maybe not.
wlad, could you please take a look?

If it's indeed fixed in 10.1, I'm not sure we must backport the fix to 10.0, as there is a viable workaround – use a smaller value of the option (if you think we should backport anyway, please do so). But if it's still in 10.1, just does not cause visible problems on whatever reason, it definitely needs fixing.

To reproduce:

• Start the server with a safe value of aria_pagecache_buffer_size
• Execute

  drop table if exists t1;

  create table t1 (pk int auto_increment primary key, i int, key(i)) engine=Aria;

  insert into t1 values (null,1),(null,2),(null,3),(null,4);

  insert into t1 select null, a.i from t1 a, t1 b, t1 c, t1 d, t1 e, t1 f, t1 g, t1 h, t1 i;

• restart server with a problematic value of aria_pagecache_buffer_size (see above, depending on what you are trying to reproduce, the error or the crash);
• run

  mysql -uroot test -e "select * from t1" > t1.data

Setting aria_pagecache_buffer_size to 4G seems to work. Thanks for your help!

pushed to 5.5 , serious