What can I do about this MariaDB 10.0 error? I have a serious error that crashes the mariadb service, and it won't start up again until I delete the database folder in the data directory of the database I was working on at the time. Here is the .err file printout. Anyone know what to do about this?

2015-02-21 13:48:23 7dc InnoDB: FTS Optimize Removing table bolingerfield/tag
2015-02-21 13:49:44 4bc4  InnoDB: Error: space id and page n:o stored in the page
InnoDB: read in are 13924:3, should be 13877:3!
2015-02-21 13:49:44 4bc4  InnoDB: Error: space id and page n:o stored in the page
InnoDB: read in are 13924:1, should be 13877:1!
2015-02-21 13:50:23 798  InnoDB: Assertion failure in thread 1944 in file btr0btr.cc line 713
InnoDB: Failing assertion: mach_read_from_4(seg_header + FSEG_HDR_SPACE) == space
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
You may have moved around manually the tablespaces or improperly importing the tables physically. The error assertion is a detection by MySQL InnoDB that pages have internal values that do not correspond to their physical location, thus forcing the kill of the server to avoid further corruption.

I have very very rarely seen that as a problem due to InnoDB programming (at least on upstream and stable MySQL), and more usually due to a problem in datafile or configuration management by an operator. While it should be possible to go back to a consistent state, without knowing more about what kind of processes you have performed, I would start by recommending performing a bull backup of your system so no data is lost.