Heroku App Crashed: Heroku/Syslog drain

I have recently installed it on Heroku via one click install button and it installed from latest master repo. After a while I started receiving Heroku/Syslog drain messages and finally after an hour my server got crashed with following log:

App crashed: Heroku/Syslog drain
2018-10-02 10:53:35.730 377 <158>1 2018-10-02T10:53:35.559454+00:00 heroku router - - sock=client at=warning code=H27 desc="Client Request Interrupted" method=GET path="/sockjs/info?cb=ow4jgzx5ws" host=evaluation-rc.herokuapp.com request_id=e34eda57-bd3e-4c94-9ee4-a11f4c1c47c0 fwd="119.160.98.45" dyno=web.1 connect=1ms service=2ms status=499 bytes= protocol=https
2018-10-02 10:53:37.857 314 <158>1 2018-10-02T10:53:37.560874+00:00 heroku router - - at=info method=GET path="/sounds/chelle.mp3" host=evaluation-rc.herokuapp.com request_id=3fdacaa2-5c4e-48ec-82e9-3b17de36b4b6 fwd="119.160.98.45" dyno=web.1 connect=1ms service=4ms status=206 bytes=307 protocol=https
2018-10-02 10:53:39.689 306 <158>1 2018-10-02T10:53:39.494312+00:00 heroku router - - at=info method=GET path="/_timesync" host=evaluation-rc.herokuapp.com request_id=876c39cb-57c3-483c-85f2-ef8a8d1f0ebe fwd="119.160.98.45" dyno=web.1 connect=1ms service=3ms status=200 bytes=282 protocol=https
2018-10-02 10:56:32.852 309 <158>1 2018-10-02T10:56:32.671963+00:00 heroku router - - at=info method=GET path="/assets/logo" host=evaluation-rc.herokuapp.com request_id=410fb506-c73b-496b-8b18-085d28b4367c fwd="119.160.98.45" dyno=web.1 connect=1ms service=54ms status=304 bytes=225 protocol=https
2018-10-02 10:56:32.950 312 <158>1 2018-10-02T10:56:32.751384+00:00 heroku router - - at=info method=GET path="/sounds/door.mp3" host=evaluation-rc.herokuapp.com request_id=989eb33e-614d-4481-ba39-7fba0edc078b fwd="119.160.98.45" dyno=web.1 connect=1ms service=8ms status=206 bytes=307 protocol=https
2018-10-02 11:01:47.053 306 <158>1 2018-10-02T11:01:46.666262+00:00 heroku router - - at=info method=GET path="/_timesync" host=evaluation-rc.herokuapp.com request_id=63f9069b-8f02-4a05-9c59-8e249cf3c287 fwd="119.160.98.45" dyno=web.1 connect=1ms service=2ms status=200 bytes=282 protocol=https
2018-10-02 11:12:48.027 306 <158>1 2018-10-02T11:12:47.745190+00:00 heroku router - - at=info method=GET path="/_timesync" host=evaluation-rc.herokuapp.com request_id=adef92bb-c728-42a8-b1b2-65bfd5c8a8b5 fwd="119.160.98.45" dyno=web.1 connect=1ms service=2ms status=200 bytes=282 protocol=https
2018-10-02 11:22:06.036 328 <158>1 2018-10-02T11:22:05.867581+00:00 heroku router - - at=info method=GET path="/avatar/%40general?_dc=undefined" host=evaluation-rc.herokuapp.com request_id=5228ec83-c7a8-4e68-b07b-e8a81836d367 fwd="119.160.98.45" dyno=web.1 connect=1ms service=6ms status=304 bytes=346 protocol=https
2018-10-02 12:06:07.392 126 <45>1 2018-10-02T12:06:07.044620+00:00 heroku web.1 - - Process exited with status 143
2018-10-02 12:14:22.404 126 <45>1 2018-10-02T12:14:22.094714+00:00 heroku web.1 - - Process exited with status 137
2018-10-02 12:14:23.236 337 <158>1 2018-10-02T12:14:23.075312+00:00 heroku router - - at=error code=H10 desc="App crashed" method=GET path="/sockjs/info?cb=mtd6f7pqgj" host=evaluation-rc.herokuapp.com request_id=8dc19960-2821-4c2f-9834-f1c09c73296f fwd="119.160.98.45" dyno= connect= service= status=503 bytes= protocol=https

The report only names a Heroku one-click installation and provides router and process logs; begin by reproducing the deployment and reviewing runtime logs around process exits 143 and 137. Done means identifying a reproducible cause and documenting or fixing it, but no source file or test is named.