10.3.8-MariaDB crashes in MacOS every time with [ERROR] mysqld got signal 6

MariaDB is crashing every time with [ERROR] mysqld got signal 6. I tried restarting the system and reinstalled few times with home-brew still I am getting this crash as soon as I connect from my app. Here are the steps.
1. Install mariadb using home-brew
2. Set the root password
3. Connect using MySQLWorkbench with root
4. Create the database with all the tables around 10.
5. Get results by executing few select statements in MySQLWorkbench like select count from information_schema.processlist; SHOW VARIABLES LIKE 'open%'; and show variables like 'max_connections';
6. Run my Scala app from IntelliJ IDEA
7. Now my app hangs or says not able to connect to database server after couple of statements executed. The same code was working fine in the previous mariadb couple of months back.
8. Try executing the above same queries in MySQLWorkbench and it says 'Error Code: 2013. Lost connection to MySQL server during query'

Here is the log file content from /usr/local/var/mysql/xxxxxxx-MacBook-Air.local.err

2018-08-08 17:06:59 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-08-08 17:06:59 0 [Note] InnoDB: Uses event mutexes
2018-08-08 17:06:59 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2018-08-08 17:06:59 0 [Note] InnoDB: Number of pools: 1
2018-08-08 17:06:59 0 [Note] InnoDB: Using SSE2 crc32 instructions
2018-08-08 17:06:59 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-08-08 17:06:59 0 [Note] InnoDB: Completed initialization of buffer pool
2018-08-08 17:06:59 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2018-08-08 17:06:59 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2018-08-08 17:06:59 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2018-08-08 17:06:59 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2018-08-08 17:06:59 0 [Note] InnoDB: Waiting for purge to start
2018-08-08 17:06:59 0 [Note] InnoDB: 10.3.8 started; log sequence number 1630824; transaction id 21
2018-08-08 17:06:59 0 [Note] InnoDB: Loading buffer pool(s) from /usr/local/var/mysql/ib_buffer_pool
2018-08-08 17:06:59 0 [Note] Plugin 'FEEDBACK' is disabled.
2018-08-08 17:06:59 0 [Note] InnoDB: Buffer pool(s) load completed at 180808 17:06:59
2018-08-08 17:06:59 0 [Note] Server socket created on IP: '::'.
2018-08-08 17:06:59 0 [Note] Reading of all Master_info entries succeded
2018-08-08 17:06:59 0 [Note] Added new Master_info '' to hash table
2018-08-08 17:06:59 0 [Note] /usr/local/opt/mariadb/bin/mysqld: ready for connections.
Version: '10.3.8-MariaDB' socket: '/tmp/mysql.sock' port: 3306 Homebrew
mysqld(3445,0x700005b50000) malloc: *** error for object 0x7faddf431180: incorrect checksum for freed object - object was probably modified after being freed.

• • • set a breakpoint in malloc_error_break to debug
      180808 17:13:16 [ERROR] mysqld got signal 6 ;
      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 https://mariadb.com/kb/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.3.8-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=12
max_threads=153
thread_count=18
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467396 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fade1097e08
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...
stack_bottom = 0x700005b4fe90 thread_stack 0x49000