php - mysql crashed(mysql has gone away) while getting gmail api data and storing it in the database -

while getting data from gmail , storing in databas. mysql database crashes. here latest log latest crash

2017-07-28 15:50:10 3708 [note] innodb: using mutexes ref count buffer pool pages 2017-07-28 15:50:10 3708 [note] innodb: innodb memory heap disabled 2017-07-28 15:50:10 3708 [note] innodb: mutexes , rw_locks use windows interlocked functions 2017-07-28 15:50:10 3708 [note] innodb: _mm_lfence() , _mm_sfence() used memory barrier 2017-07-28 15:50:10 3708 [note] innodb: compressed tables use zlib 1.2.3 2017-07-28 15:50:10 3708 [note] innodb: using generic crc32 instructions 2017-07-28 15:50:10 3708 [note] innodb: initializing buffer pool, size = 16.0m 2017-07-28 15:50:10 3708 [note] innodb: completed initialization of buffer pool 2017-07-28 15:50:11 3708 [note] innodb: highest supported file format barracuda. 2017-07-28 15:50:11 3708 [note] innodb: log sequence numbers 1835037 , 1835037 in ibdata files not match log sequence number 980584530 in ib_logfiles! 2017-07-28 15:50:11 3708 [note] innodb: restoring possible half-written data pages doublewrite buffer... 2017-07-28 15:50:12 3708 [note] innodb: 128 rollback segment(s) active. 2017-07-28 15:50:12 3708 [note] innodb: waiting purge start 2017-07-28 15:50:12 3708 [note] innodb:  percona xtradb (http://www.percona.com) 5.6.35-80.0 started; log sequence number 980584530 2017-07-28 15:50:12 12048 [note] innodb: dumping buffer pool(s) not yet started 2017-07-28 15:50:12 3708 [note] plugin 'feedback' disabled. 2017-07-28 15:50:12 3708 [note] server socket created on ip: '::'. 2017-07-28 15:50:12 3708 [note] c:\xampp\mysql\bin\mysqld.exe: ready connections. version: '10.1.22-mariadb'  socket: ''  port: 3306  mariadb.org binary distribution 2017-07-28 15:51:37 2b10  innodb: error: space id , page n:o stored in page innodb: read in 2259217641:2609242579, should 0:379! 2017-07-28 15:51:37 11024 [note] innodb: log sequence number @ start 3113380305 , end 3923956440 not match. 2017-07-28 15:51:37 11024 [error] innodb: corruption: block in space_id 0 in file c:\xampp\mysql\data\ibdata1 corrupted. 2017-07-28 15:51:37 11024 [error] innodb: based on page type page type corrupted (55158) 2017-07-28 15:51:37 11024 [error] innodb: database page corruption on disk or failed 2017-07-28 15:51:37 11024 [error] innodb: space 0 file c:\xampp\mysql\data\ibdata1 read of page 379. 2017-07-28 15:51:37 11024 [error] innodb: may have recover backup. 2017-07-28 15:51:37 2b10 innodb: page dump in ascii , hex (16384 bytes):  len 16384; hex (lots of hex follows) innodb: end of page dump 2017-07-28 15:51:38 2b10 innodb: uncompressed page, stored checksum in field1 1165101849, calculated checksums field1: crc32 455176142, innodb 202543763, none 3735928559, stored checksum in field2 3577157157, calculated checksums field2: crc32 455176142, innodb 1083534192, none 3735928559, page lsn 736093480 3113380305, low 4 bytes of lsn @ page end 3923956440, page number (if stored page already) 2609242579, space id (if created >= mysql-4.1.1 , stored already) 2259217641 innodb: page type 55158 meaning page type corrupted 2017-07-28 15:51:38 11024 [error] innodb: possible operatingsystem has corrupted own file cache. 2017-07-28 15:51:38 11024 [error] innodb: , rebooting computer removes error. 2017-07-28 15:51:38 11024 [error] innodb: if corrupt page index page can try 2017-07-28 15:51:38 11024 [error] innodb: fix corruption dumping, dropping, , reimporting 2017-07-28 15:51:38 11024 [error] innodb: corrupt table. can use check 2017-07-28 15:51:38 11024 [error] innodb: table scan table corruption. 2017-07-28 15:51:38 11024 [error] innodb: see http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html forcing recovery. 2017-07-28 15:51:38 11024 [error] innodb: ending processing because of corrupt database page. 2017-07-28 15:51:38 2b10  innodb: assertion failure in thread 11024 in file buf0buf.cc line 4829 innodb: intentionally generate memory trap. innodb: submit detailed bug report http://bugs.mysql.com. innodb: if repeated assertion failures or crashes, innodb: after mysqld startup, there may innodb: corruption in innodb tablespace. please refer innodb: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html innodb: forcing recovery. 170728 15:51:38 [error] mysqld got exception 0x80000003 ; because hit bug. possible binary or 1 of libraries linked against corrupt, improperly built, or misconfigured. error can caused malfunctioning hardware.  report bug, see https://mariadb.com/kb/en/reporting-bugs  try our best scrape info diagnose problem, since have crashed,  wrong , may fail.  server version: 10.1.22-mariadb key_buffer_size=16777216 read_buffer_size=262144 max_used_connections=4 max_threads=1001 thread_count=4 possible mysqld use  key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 787106 k  bytes of memory hope that's ok; if not, decrease variables in equation. innodb: page type 42674 meaning page type corrupted 2017-07-28 15:54:19 2400 [error] innodb: possible operatingsystem has corrupted own file cache. 2017-07-28 15:54:19 2400 [error] innodb: , rebooting computer removes error. 2017-07-28 15:54:19 2400 [error] innodb: if corrupt page index page can try 2017-07-28 15:54:19 2400 [error] innodb: fix corruption dumping, dropping, , reimporting 2017-07-28 15:54:19 2400 [error] innodb: corrupt table. can use check 2017-07-28 15:54:19 2400 [error] innodb: table scan table corruption. 2017-07-28 15:54:19 2400 [error] innodb: see http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html forcing recovery. 2017-07-28 15:54:19 2400 [error] innodb: ending processing because of corrupt database page. 2017-07-28 15:54:19 960  innodb: assertion failure in thread 2400 in file buf0buf.cc line 4829 innodb: intentionally generate memory trap. innodb: submit detailed bug report http://bugs.mysql.com. innodb: if repeated assertion failures or crashes, innodb: after mysqld startup, there may innodb: corruption in innodb tablespace. please refer innodb: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html innodb: forcing recovery. 170728 15:54:19 [error] mysqld got exception 0x80000003 ; 

here table trying insert to

create table `emails` (     `id_email` int(11) not null auto_increment,     `fk_lead` int(11) not null,     `sender` varchar(200) not null,     `sender_name` varchar(200) not null,     `sender_email` varchar(200) not null,     `recipient` varchar(200) not null,     `recipient_email` varchar(200) not null,     `recipient_name` varchar(200) not null,     `gmail_id` varchar(50) not null,     `thread_id` varchar(50) not null,     `received_date` datetime not null,     `subject` varchar(500) not null,     `content` longtext null,     `deprecated` int(1) null default null,     `created_at` datetime null default null,     `last_updated` datetime null default null,     `user_agent` varchar(50) null default null,     `mime_version` varchar(10) null default null,     `content_type` varchar(100) null default null,     `originating_ip` varchar(15) null default null,     primary key (`id_email`),     unique index `gmail_id` (`gmail_id`) ) 

i think culprit base_64 content script trying insert table's column 'content'.

so everytime try run script, shows in logs. mysql server installed when installed xampp windows 10 64bit. btw, running on laptop average specs (i5 7200u, 8gb ram, 512gb ssd).