This repository has been archived by the owner on Mar 9, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
DB size grows on OS X #303
Comments
What commit SHA1 are you using? I ran your example using the latest (75f70a1) and it doesn't grow the database beyond the initial 1MB size. |
Ah, nm. I found it once I bumped the size high enough. Thanks. Will fix. |
I'm using b8dbe11 that's the last significant commit. My DB is 3072MB in size so maybe that matters. I need some time to reproduce that bug using abstract data, so will update this issue later. As the most simple way, I can hand you my 3GB blob privately, but it's better to make a test case :) Stay tuned. |
@xlab confirmed with https://gist.github.com/kemist/f2c4a6ded05fb6aeb98d |
Oh nm, didn't see your confirm ben |
Merged
CI is 💚 but can one of you confirm the fix before I merge it? |
Hey Ben, you are fast! Confirmed, db no longer grows |
💃 |
Thanks! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello. I have OS X Yosemite 10.10.2 and go1.4.1 darwin/amd64, the situation is similar to #291. It seems that #292 fix works, because DB size grows exactly by 1GB at once. The problem is, the file grows on each
bolt.Open
, the initial size of DB was 3072MBAfter ~100 seconds I've got ~103GB file and no space left on the device.
file resize error: truncate file.db: no space left on device
I can tell more details upon request, just don't know what kind of details will be useful there.
Thanks.
The text was updated successfully, but these errors were encountered: