Forum for English speaking Miranda NG users > Bug reports

Latest libmdbx (commit from 25.8.2018)

(1/3) > >>

Vulpix:
https://github.com/miranda-ng/miranda-ng/commit/c2216a4278bbbc3f breaks miranda's ability to store new messages. That actually also seems to break steam which can no longer log in, guess it depends on something.

I also honestly despise libmdbx at this point, and I wish we could either get the old mmap back (honestly there is nothing good about mdbx), or if you really need something new, migrate to like a verified solution, i.e. sqlite. I understand it'd be slow but right now it's not really fast or at least I can't tell, and the fact the db is 2x bigger, unstable and potentially liable to lose your data with 0 recovery methods is honestly the scariest possible scenario for anyone using an instant messenger aggregator client.

Please reconsider.

That or have a second miranda branch where you do database related changes.

Or at least let me verify the new build before it's pushed out, I don't mind cooperating on this.

EDIT: Tested with @Ghazan and now the change has been rolled back. Should be safe to update again. ( https://github.com/miranda-ng/miranda-ng/commit/cf57ec609dc7b02eb44433514af60bb74951e990 )

Vulpix:
After updating today and losing some data again (thank god for working jsonimport, honestly...), I give up and I don't want to use mdbx ever again :p

https://github.com/miranda-ng/miranda-ng/issues/1597 created, probably going to put a bounty on it.

Der Jude:
Yes please, this MDBX is a joke of a database driver, I'm sick and tired of hearing my HDD constantly scratch because MDBX decides for no good reason to read 100kbyte+write 400kbyte~ worth of I/O operations per second + 1mbyte/s HDD writes for prolonged time, whenever I log in at steam or discord. I never heard my HDD work because of Miranda back when MMAP was being used.

Why can't we just use MMAP as primary database for storing all messages/other stuff MMAP was good for + have secondary database in MDBX for features that cannot be supported by MMAP?
If it wont be possible to make it work with crosslinking references in both DBs then just drop MDBX whole and return to MMAP, MDBX in current form and shape is a big fat mistake.

Vulpix:
Just had another corruption happen today. Not sure what it is honestly. I even remade my profile and reimported it into clean, but seems that didn't matter. It's generally always when I'm talking to someone on discord. Also, when checking past backups, I can generally see that the size of one of the previous backups is randomly different. Like, smaller or larger by 1 megabyte, for example.

Is it possible the backup is doing this? It runs compaction before the actual backup (not a setting I can influence but I believe so). Can this be changed ? Could this be the reason? Maybe the db is so huge the backup takes long enough for some issue to occur during it?

My DB is currently 438MB.

dartraiden:
dbx_sqlite just landed in development version.

Navigation

[0] Message Index

[#] Next page