-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash: "double free or corruption (!prev)" #78
Comments
Reading crash logs:
Sounds like there is some sort of connection cleanup in the SQLite library that's messing it up. You see it happen infrequently due to the race condition (guessing from |
Would it be OK for you to join the discord channel and DM me? I am trying to reproduce the issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've been getting consistent crashes on the master server (in a master node + 1 replica setup). Both are on the latest version from the realeases page. Uptime is inconsistent. Sometimes its up for a day then crashes and sometimes it crashes within a few hours.
They're using basic configs so I might be missing an important thing that I do not know about.
The replica server has been running fine with no crashes.
Configs:
Details
Each instance is ran through the command line like
The database that it's using is 1.8GB with 4 tables of which only 1 (
videos_clean
) is being updated frequently. The master database is a replica itself to keep it separate from the production one, a script pushes changes to it every minute.Below is the output from the most recent crash.
marmot-v0.8.5-master-crashlog.txt
The text was updated successfully, but these errors were encountered: