Author Topic: Profile Crashed = unknown format  (Read 177 times)

0 Members and 1 Guest are viewing this topic.

Offline SpinalBloodTopic starter

Profile Crashed = unknown format
« on: 07 10 2020, 22:55:16 »
I know there is this solution: https://www.miranda-ng.org/en/news/unknown-profile-format

But I have this problem NOT after an update, but just a crash that happened suddenly; or rather, I had to terminate the process because miranda was frozen.

This is the second time it happened and I don't know what causaed this crash (most likely when I attempted to paste a url in the window messaging?)

I had a backup of some days earlier which is more or less ok but I lost a bit of facebook history. Is the broken profile fixable somehow?
 

Offline dartraiden

Re: Profile Crashed = unknown format
« Reply #1 on: 09 10 2020, 15:24:55 »
Download last alpha build 23402 or newer

Try
Code: [Select]
mdbx_chk.exe -i -w -v -t -1 "path\to\corrupted.dat"(backup corrupted db before any change)

if no success, try
Code: [Select]
mdbx_chk.exe -i -w -v -t -2 "path\to\corrupted.dat"
please report here about results :)
_██_
(°ᴗƪ)
 
The following users thanked this post: SpinalBlood

Offline SpinalBloodTopic starter

Re: Profile Crashed = unknown format
« Reply #2 on: 15 10 2020, 02:23:11 »
It worked!  :) (with the first command). Thanks!

Here's the log: I did it with two crashed profiles since it happened also on another backup profile used in the meanwhile:

Spoiler
Code: [Select]
mdbx_chk v0.9.1-18-g1d31ebdc1c (2020-10-08T01:50:18+03:00, T-5cbfdfdc65b62937f7f
c927e55cec6304bf04f7c)
Running for C:\Program Files (x86)\Miranda\Profiles\Profile\profile.dat in 'read
-write' mode...
 ~ filesize mismatch (expect 524288000b/128000p, have 526385152b/128512p)
 - monopolistic mode
 - current boot-id unavailable
 - pagesize 4096 (4096 system), max keysize 1300..1344, max readers 122
 - mapsize 536870912 (512.00 Mb)
 - dynamic datafile: 12288 (12.00 Kb) .. 536870912 (512.00 Mb), +1048576 (1.00 M
b), -524288 (512.00 Kb)
 - current datafile: 524288000 (500.00 Mb), 128000 pages
                     WARNING: Due Windows system limitations a file couldn't
                     be truncated while the database is opened. So, the size
                     database file of may by large than the database itself,
                     until it will be closed or reopened in read-write mode.
 - transactions: recent 6087503, latter reader 6087503, lag 0
 - meta-0: weak-unknown (no boot-id txn#6087502, stay
 - meta-1: weak-unknown (no boot-id txn#6087503, head, forced for checking
 - meta-2: weak-unknown (no boot-id txn#6087501, tail
Traversal b-tree by txn#6087503...
 - found 'contacts' area
 - found 'crypto' area
 - found 'eventids' area
 - found 'events' area
 - found 'eventsrt' area
 - found 'global' area
 - found 'modules' area
 - found 'settings' area
 - pages: walked 127844, left/unused 32
 - summary: average fill 95.0%, 0 problems
Processing '@MAIN'...
 - key-value kind: usual-key => single-value
 - summary: 8 records, 0 dups, 57 key's bytes, 384 data's bytes, 0 problems
Processing '@GC'...
 - key-value kind: ordinal-key => single-value
 - fixed key-size 8
 - summary: 3 records, 0 dups, 24 key's bytes, 140 data's bytes, 0 problems
 - space: 131072 total pages, backed 128000 (97.7%), allocated 127876 (97.6%), a
vailable 3223 (2.5%)
Processing 'contacts'...
 - key-value kind: ordinal-key => single-value
 - last modification txn#6087502
 - fixed key-size 4
 - summary: 1051 records, 0 dups, 4204 key's bytes, 16816 data's bytes, 0 proble
ms
Processing 'crypto'...
 - key-value kind: usual-key => single-value
 - last modification txn#6
 - summary: 3 records, 0 dups, 25 key's bytes, 64 data's bytes, 0 problems
Processing 'eventids'...
 - key-value kind: usual-key => single-value
 - last modification txn#6087337
 - summary: 4052 records, 0 dups, 120658 key's bytes, 16208 data's bytes, 0 prob
lems
Processing 'events'...
 - key-value kind: ordinal-key => single-value
 - last modification txn#6087502
 - fixed key-size 4
 - summary: 4767023 records, 0 dups, 19068092 key's bytes, 294339613 data's byte
s, 0 problems
Processing 'eventsrt'...
 - key-value kind: usual-key => single-value
 - last modification txn#6087500
 - summary: 4766974 records, 0 dups, 76271584 key's bytes, 4766974 data's bytes,
 0 problems
Processing 'global'...
 - key-value kind: ordinal-key => single-value
 - last modification txn#66215
 - fixed key-size 4
 - summary: 2 records, 0 dups, 8 key's bytes, 24 data's bytes, 0 problems
Processing 'modules'...
 - key-value kind: ordinal-key => single-value
 - last modification txn#4848807
 - fixed key-size 4
 - summary: 178 records, 0 dups, 712 key's bytes, 1981 data's bytes, 0 problems
Processing 'settings'...
 - key-value kind: usual-key => single-value
 - last modification txn#6087503
 - summary: 64335 records, 0 dups, 1125839 key's bytes, 859034 data's bytes, 0 p
roblems
 = Performing turn to the specified meta-page (1) due to successful check!
No error is detected, elapsed 4.242 seconds


Spoiler
Code: [Select]
mdbx_chk v0.9.1-18-g1d31ebdc1c (2020-10-08T01:50:18+03:00, T-5cbfdfdc65b62937f7f
c927e55cec6304bf04f7c)
Running for C:\Program Files (x86)\Miranda\copia di profili\prof\corrupted.dat i
n 'read-write' mode...
 ~ skipped update meta.geo in recovery mode: from l3-n128000-u131072/s128-g256,
to l3-n128512-u131072/s128-g256
 - monopolistic mode
 - current boot-id unavailable
 - pagesize 4096 (4096 system), max keysize 1300..1344, max readers 122
 - mapsize 536870912 (512.00 Mb)
 - dynamic datafile: 12288 (12.00 Kb) .. 536870912 (512.00 Mb), +1048576 (1.00 M
b), -524288 (512.00 Kb)
 - current datafile: 526385152 (502.00 Mb), 128512 pages
                     WARNING: Due Windows system limitations a file couldn't
                     be truncated while the database is opened. So, the size
                     database file of may by large than the database itself,
                     until it will be closed or reopened in read-write mode.
 - transactions: recent 6147171, latter reader 6147170, lag 1
 - meta-0: weak-unknown (no boot-id txn#6147171, head
 - meta-1: weak-unknown (no boot-id txn#6147170, stay, forced for checking
 - meta-2: weak-unknown (no boot-id txn#6147169, tail
Traversal b-tree by txn#6147170...
 - found 'contacts' area
 - found 'crypto' area
 - found 'eventids' area
 - found 'events' area
 - found 'eventsrt' area
 - found 'global' area
 - found 'modules' area
 - found 'settings' area
 - pages: walked 127861, left/unused 31
 - summary: average fill 95.0%, 0 problems
Processing '@MAIN'...
 - key-value kind: usual-key => single-value
 - summary: 8 records, 0 dups, 57 key's bytes, 384 data's bytes, 0 problems
Processing '@GC'...
 - key-value kind: ordinal-key => single-value
 - fixed key-size 8
 - summary: 3 records, 0 dups, 24 key's bytes, 136 data's bytes, 0 problems
 - space: 131072 total pages, backed 128512 (98.0%), allocated 127892 (97.6%), a
vailable 3202 (2.4%)
Processing 'contacts'...
 - key-value kind: ordinal-key => single-value
 - last modification txn#6147170
 - fixed key-size 4
 - summary: 1051 records, 0 dups, 4204 key's bytes, 16816 data's bytes, 0 proble
ms
Processing 'crypto'...
 - key-value kind: usual-key => single-value
 - last modification txn#6
 - summary: 3 records, 0 dups, 25 key's bytes, 64 data's bytes, 0 problems
Processing 'eventids'...
 - key-value kind: usual-key => single-value
 - last modification txn#6143342
 - summary: 4086 records, 0 dups, 120000 key's bytes, 16344 data's bytes, 0 prob
lems
Processing 'events'...
 - key-value kind: ordinal-key => single-value
 - last modification txn#6147170
 - fixed key-size 4
 - summary: 4767437 records, 0 dups, 19069748 key's bytes, 294375997 data's byte
s, 0 problems
Processing 'eventsrt'...
 - key-value kind: usual-key => single-value
 - last modification txn#6147168
 - summary: 4767388 records, 0 dups, 76278208 key's bytes, 4767388 data's bytes,
 0 problems
Processing 'global'...
 - key-value kind: ordinal-key => single-value
 - last modification txn#66215
 - fixed key-size 4
 - summary: 2 records, 0 dups, 8 key's bytes, 24 data's bytes, 0 problems
Processing 'modules'...
 - key-value kind: ordinal-key => single-value
 - last modification txn#4848807
 - fixed key-size 4
 - summary: 178 records, 0 dups, 712 key's bytes, 1981 data's bytes, 0 problems
Processing 'settings'...
 - key-value kind: usual-key => single-value
 - last modification txn#6147169
 - summary: 64327 records, 0 dups, 1125731 key's bytes, 859019 data's bytes, 0 p
roblems
 = Performing turn to the specified meta-page (1) due to successful check!
No error is detected, elapsed 4.943 seconds


Not sure if the report is ordinary and I can consider the profiles safe now, especially about the following:

Spoiler
Code: [Select]
b), -524288 (512.00 Kb)
 - current datafile: 526385152 (502.00 Mb), 128512 pages
                     WARNING: Due Windows system limitations a file couldn't
                     be truncated while the database is opened. So, the size
                     database file of may by large than the database itself,
                     until it will be closed or reopened in read-write mode.


Is the size a problem? Because about the sudden crashes, I'm wondering if they were related to a size issue, exceededing 512.000 kb?

This profile is pretty big and was recently converted by an older miranda that used the dbx_mmap and went from 3xx mb to almost 500 mb

Another thing to notice: after the migration, for some reason the history++ search was VERY slow, but after this recovery command, it seems to be now much faster (probably like it used to be before the migration?)
« Last Edit: 15 10 2020, 02:26:09 by SpinalBlood »
 

Offline trolrolo

  • Newbie
  • *
  • Posts: 1
  • Karma: 0
Re: Profile Crashed = unknown format
« Reply #3 on: 15 10 2020, 05:34:35 »
I have similar problem. I have version 0.95.12 build 23274 since about 2 months.
After upgrade to 0.95.12 my profile has being corrupted several times. I'm restoring it from backup. I have backup plugin. Before the upgrade there was no such problem - never. I have been using Miranda since years..
It usually happened after Windows restart (normal restart. Start->Restart computer) or process termination Miranda from Task Manager
I known the solutions with compacting. It's better after compacting, but not solved the problem.

Today my profile was corrupted once again after computer restart because of Windows Update. Windows Update wanted me to restart computer, I have restarted and after log in there was an information from Miranda about corrupted profile.

It’s being so much annoying. Is there any solution for this ? My profile file.dat is not big about 23Mb

Another problem is that sometimes Mirranda is not responding it consumes about 20% of CPU. The only solutions is to kill process. But after killing process profile can be corrupted.

In plugins I have 2 dbx plugins:
db_mdbx.dll  0.95.9.1
db_mmap.dll 0.95.8.1
« Last Edit: 15 10 2020, 05:46:13 by trolrolo »
 

Offline dartraiden

Re: Profile Crashed = unknown format
« Reply #4 on: 15 10 2020, 16:36:07 »
It’s being so much annoying. Is there any solution for this ?
DbAutobackups and more frequent backups

or https://forum.miranda-ng.org/index.php?topic=6117.msg27671#msg27671
_██_
(°ᴗƪ)
 

Offline dartraiden

Re: Profile Crashed = unknown format
« Reply #5 on: 15 10 2020, 17:13:00 »
Is the size a problem?
Size is not problem on x64 builds.
_██_
(°ᴗƪ)
 

Offline dartraiden

Re: Profile Crashed = unknown format
« Reply #6 on: 15 10 2020, 17:13:52 »
history++
H++ is slow crap, we suggest to use NewStory as History Viewer
_██_
(°ᴗƪ)
 

Offline SpinalBloodTopic starter

Re: Profile Crashed = unknown format
« Reply #7 on: 15 10 2020, 20:18:02 »
I'm using x86 version, has the profile size a max capacity then? If I'll have problems because of this, I may switch to x64

I just checked NewStory, very similar, but it doesn't seem like it has global search and hotkeys (very handy functions that history++ has)...

 

Offline Vulpix

Re: Profile Crashed = unknown format
« Reply #8 on: 16 10 2020, 10:34:49 »
I'm using x86 version, has the profile size a max capacity then? If I'll have problems because of this, I may switch to x64

I just checked NewStory, very similar, but it doesn't seem like it has global search and hotkeys (very handy functions that history++ has)...

I tried newstory too, but I couldn't find bookmarks and search was also a bit clunky, so I have to agree with SpinalBlood... can we somehow get NewStory to implement these? :D
 

Offline dartraiden

Re: Profile Crashed = unknown format
« Reply #9 on: 16 10 2020, 14:36:05 »
I'm using x86 version, has the profile size a max capacity then?
~300 Mb
_██_
(°ᴗƪ)
 

Offline dartraiden

Re: Profile Crashed = unknown format
« Reply #10 on: 16 10 2020, 14:36:52 »
can we somehow get NewStory to implement these?
Feel free to open tickets ;)
_██_
(°ᴗƪ)
 

Offline SpinalBloodTopic starter

Re: Profile Crashed = unknown format
« Reply #11 on: 16 10 2020, 17:37:37 »
~300 Mb

I'm not sure then because before updating it was already more than 300mb (never crashed); well I'll keep backup / monitoring crashes for now