PostgreSQL on dev constantly restarts

I see these error messages:

2017-08-10_22:09:40.02762 PANIC:  semop(id=174817293) failed: Invalid argument
2017-08-10_22:09:40.02765 STATEMENT:  COMMIT
2017-08-10_22:09:40.02979 PANIC:  semop(id=174817293) failed: Invalid argument
2017-08-10_22:09:40.02979 STATEMENT:  COMMIT
2017-08-10_22:09:40.16069 LOG:  server process (PID 20998) was terminated by signal 6: Aborted
2017-08-10_22:09:40.16071 DETAIL:  Failed process was running: COMMIT
2017-08-10_22:09:40.16071 LOG:  terminating any other active server processes
2017-08-10_22:09:40.17187 WARNING:  terminating connection because of crash of another server process
2017-08-10_22:09:40.17188 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2017-08-10_22:09:40.17188 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2017-08-10_22:09:40.17188 WARNING:  terminating connection because of crash of another server process
2017-08-10_22:09:40.17208 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2017-08-10_22:09:40.17208 WARNING:  terminating connection because of crash of another server process
2017-08-10_22:09:40.17208 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2017-08-10_22:09:40.17209 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2017-08-10_22:09:40.17209 WARNING:  terminating connection because of crash of another server process
2017-08-10_22:09:40.17209 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2017-08-10_22:09:40.17209 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2017-08-10_22:09:40.17301 LOG:  archiver process (PID 20973) exited with exit code 1
2017-08-10_22:09:40.17980 WARNING:  terminating connection because of crash of another server process
2017-08-10_22:09:40.17981 DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2017-08-10_22:09:40.17981 HINT:  In a moment you should be able to reconnect to the database and repeat your command.
2017-08-10_22:09:40.22266 LOG:  all server processes terminated; reinitializing
2017-08-10_22:09:40.22269 LOG:  could not remove shared memory segment "/PostgreSQL.856261843": No such file or directory
2017-08-10_22:09:40.22269 LOG:  semctl(174424065, 0, IPC_RMID, ...) failed: Invalid argument
2017-08-10_22:09:40.22270 LOG:  semctl(174456834, 0, IPC_RMID, ...) failed: Invalid argument
2017-08-10_22:09:40.22270 LOG:  semctl(174489603, 0, IPC_RMID, ...) failed: Invalid argument
2017-08-10_22:09:40.22270 LOG:  semctl(174522372, 0, IPC_RMID, ...) failed: Invalid argument
2017-08-10_22:09:40.22270 LOG:  semctl(174555141, 0, IPC_RMID, ...) failed: Invalid argument
2017-08-10_22:09:40.22271 LOG:  semctl(174587910, 0, IPC_RMID, ...) failed: Invalid argument
2017-08-10_22:09:40.22271 LOG:  semctl(174620679, 0, IPC_RMID, ...) failed: Invalid argument
2017-08-10_22:09:40.22271 LOG:  semctl(174653448, 0, IPC_RMID, ...) failed: Invalid argument
2017-08-10_22:09:40.22271 LOG:  semctl(174686217, 0, IPC_RMID, ...) failed: Invalid argument
2017-08-10_22:09:40.22272 LOG:  semctl(174718986, 0, IPC_RMID, ...) failed: Invalid argument
2017-08-10_22:09:40.22272 LOG:  semctl(174751755, 0, IPC_RMID, ...) failed: Invalid argument
2017-08-10_22:09:40.22272 LOG:  semctl(174784524, 0, IPC_RMID, ...) failed: Invalid argument
2017-08-10_22:09:40.22272 LOG:  semctl(174817293, 0, IPC_RMID, ...) failed: Invalid argument
2017-08-10_22:09:40.22272 LOG:  semctl(174850062, 0, IPC_RMID, ...) failed: Invalid argument
2017-08-10_22:09:40.48606 FATAL:  the database system is in recovery mode
2017-08-10_22:09:40.48607 LOG:  database system was interrupted; last known up at 2017-08-10 22:07:25 GMT
2017-08-10_22:09:40.48613 FATAL:  the database system is in recovery mode
2017-08-10_22:09:40.48677 FATAL:  the database system is in recovery mode
2017-08-10_22:09:40.48701 FATAL:  the database system is in recovery mode
2017-08-10_22:09:40.48723 FATAL:  the database system is in recovery mode
2017-08-10_22:09:40.49129 FATAL:  the database system is in recovery mode
2017-08-10_22:09:40.49130 FATAL:  the database system is in recovery mode
2017-08-10_22:09:40.53513 FATAL:  the database system is in recovery mode
2017-08-10_22:09:40.53671 FATAL:  the database system is in recovery mode
2017-08-10_22:09:40.59933 FATAL:  the database system is in recovery mode
2017-08-10_22:09:40.60033 FATAL:  the database system is in recovery mode
2017-08-10_22:09:40.77375 LOG:  database system was not properly shut down; automatic recovery in progress
2017-08-10_22:09:40.78111 LOG:  redo starts at 3DA/C6000060
2017-08-10_22:09:40.78236 LOG:  invalid record length at 3DA/C902BB20: wanted 24, got 0