Error on parsing new messages.json files

[The-Kitchen-Sink]

Hi there Thanks for writing such a useful piece of software (ive used it for years to read my old skype db - only did i discover last week i could merge in the archives i had on file so was doing that when ive run into this error)

Im having issues getting skyperious 5.4.1 to parse a recent messages.json file from a skype export (export date 11th of April 2024) the export opens perfectly ok using the skype-parser provided by microsoft

If i do the following in the application file => new => import from skype archive it finds only a handful of the messages in the whole archive (150 from a 250mb+ messages.json file)

The anonymised log is attached SkyperiousLog.txt

i should note my skype account is old and just uses a skype name rather than being associated with an email address.

Any ideas what might be wrong? I get similar errors using an export from 22 Jan 23. However an old archive from March 22 works ok

[suurjaak]

Confirmed, I got the same result when I made a fresh export from Skype and imported it in Skyperious. Looks like Microsoft has changed the export contents somewhat, and as a result 1:1 chats were not imported.

Can you try with https://erki.lap.ee/stuff/skyperious_5.5.dev2_x64.exe and see how it fares?

[The-Kitchen-Sink]

Hi there

sorry it took so long to get back to you

the new version appears to work, with some errors in the log file (see attached log) along with a couple of sample messages from the json file that correspond to the errors

The other thing i noted was huge windows explorer process usage while running 45% on my ryzen 3600x (6 core 12 thread) even without having the folder open where the messages.json or the new db file were being created skyperious itself only consumed between 5-12% resources (and it did appear to take a very long time compared to the earlier version)

samplemessages.txt SkyperiousLog5_5_Dev2.txt

[suurjaak]

Those errors seem normal - the messages are file transfers, so Skyperious tries to parse the file information, but the message body is empty (presumably because the messages appears to have been deleted), so it logs the error and continues on to the next message.

Are there still messages visible in the official UI but missing in your import result?

Yes, the import can take a good long time; your earlier imports went faster because a lot of chats got skipped with all their messages. But I didn't quite get that about the resource usage - if Skyperious was taking 5-12% of CPU, what was taking 45%?

[suurjaak]

Released v5.5 with the fix.