-
Notifications
You must be signed in to change notification settings - Fork 34
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
MemoryError #38
Comments
Is there more information on this error in the log window (from menu Help -> Show log window)? |
Assuming the "main corrupt.db" is a rename I gave to the file. And I checked the file with the tool, it's not considered as corrupted. I even tried with other .db. Thanks ! 01:40:01.159 Opened C:\Users\FloGaming64\Documents\Skype db\main corrupt.db (38.68 MB).
01:59:12.120 Conversations and participants: retrieving all (C:\Users\FloGaming64\Documents\Skype db\main.db). |
Looks like there is a message with some very unusual structure. Can you run this test version: http://erki.lap.ee/skyperious/skyperious_3.5a_test_x64.exe. It will write a file named parselog.txt to its current directory during merging. Try the merge again and once the error occurs, open the text file and send me its last entry (you can censor any personal information). |
Thanks, I'll test with this version and will come back. |
Here it is : Parsing message with body: It was an automated message sent to see a MMS. |
And by the way, the error occured way quickier than with the previous version of your software. I'm not entirely sure it was the same error though. |
I fear that GitHub might have removed some of the message formatting. Can you put it on a pastebin, like https://bpaste.net? Can you also paste the new error from the log window? |
Ah yea, didn't even see. https://bpaste.net/show/97ab9b69106d And there is this message at the bottom of the Skyperious windows : |
Aha, that is actually a different error indeed, brought on by yet unpublished changes in Skyperious. I fixed this error, can you try again: |
Ok ! EDIT : Seems we're heading to the original error, the merging stopped progressing. |
So here we go : The last entry in the parselog : |
Thank you, with this information I can figure out the problem. |
Ok, I think I have it fixed now. Can you try doing the merge with this version: And does the thing with first time program launch shutting down still happen? |
Hey. I was unable to try if it fixed the problem. |
It worked just fine ! Perfect ! Thanks ! |
Glad to hear the merge problem is solved. An officially fixed release will come after a while. But the program shutting down on first launch is troubling. And puzzling. This is something I've never encountered before. What operating system are you using - Windows 7, 64bit? |
It's not really shutting down, it's just a reboot. The window opens, then closes, then opens again. |
Well, that is.. rather strange. I'm afraid I'm at a loss about this one. |
Memory fix pushed to official release. |
Hi,
First time I ever come on GitHub, so I don't know how issues got to be mentionned.
I tried to merge 2 .db (got 4 of this to merge actually), and a "MemoryError" occured.
Is there a way to get through this ?
I even tried to merge only one (very big) chat from a .db to another, and still this "MemoryError" occured.
Thanks !
The text was updated successfully, but these errors were encountered: