meganz
[Bug] MEGAsync keep crashing every time when starting synchronization
This is my setup:
PC A - Windows 10 x64 PC B - Windows 7 x64
MEGAsync version 4.3.7 running on both PCs.
PC A at work, PC B at home.
When I am at work, MEGAsynch updates the MEGA server with the newly added/modified files.
When I come back home, I log into PC B (which is already powered on and with MEGAsynch already running), MEGAsync icon change with the rotating arrow indicating synchronization, and after few seconds it crashes:
MEGAprivate ERROR DUMP
Application: MEGAsync [64 bit]
Hash: cefdbd888d5992f7ede49195395dd476
Version code: 4307.0
Timestamp: 1605527264907
Module name: MEGAsync.exe
Operating system: Windows 6.1.7601
Error info:
Unhandled exception 0xC0000005 at 0x126AFC(MEGAsync.exe)
Stacktrace:
#0 0x126AFC (MEGAsync.exe)
#1 0x170970 (MEGAsync.exe)
#2 0x134918 (MEGAsync.exe)
#3 0x12B535 (MEGAsync.exe)
#4 0x11959A (MEGAsync.exe)
#5 0x1DE45D (MEGAsync.exe)
#6 0x20A249 (MEGAsync.exe)
#7 0x2F1E7 (Qt5Core.dll)
#8 0x159BD (kernel32.dll)
#9 0x2A2E1 (ntdll.dll)
This happens every time I come back home. I log into PC B, MEGAsynch detects the newly added/modified files, it crashes with the above popup, and I have to manually run it again. Every, single, time.
I hope a solution exists for this issue because it is starting to be a really annoying and serious bug. I don't know what changed in the previous MEGAsync versions, but this issue didn't happen before.
Update: the MEGAsync crash on PC B also happened after powering it down, rebooting, and starting MEGAsync the first time after reboot.
The second time I started it, MEGAsync didn't crash. So, this serious bug even happens in this case.
Hi @pidgeon777 , thanks very much for the concise bug report. We are keen to reproduce and fix this problem. Could you please let us know what sort of changes you have made to the account before the crash occurs - deleting or moving files or folders, perhaps between syncs? Or just adding files/folders? And is the sync into your own account or a shared folder? Whatever you can tell us about your setup to narrow down how to reproduce the problem would be appreciated. Thanks very much. Oh and in your last comment, you seem to be saying the crash did NOT occur on the second restart? thanks
Hi, thanks for the prompt reply.
Could you please let us know what sort of changes you have made to the account before the crash occurs - deleting or moving files or folders, perhaps between syncs? Or just adding files/folders?
When at work (PC A), I added/removed/modified files and folders, for a total of no more than 200/300 items. Less than 100 MB in total.
When I come back home (PC B), I login back to access Windows 7, MEGAsync wakes up from idle and detect all of those changes, but after 10 seconds it crashes. I have to start it a second time to avoid this.
And is the sync into your own account or a shared folder?
In both of my PCs I'm sharing the whole account through a single folder and its subdirectories. So:
PC A - C:\Work\MEGA PC B - D:\Cloud\MEGA
you seem to be saying the crash did NOT occur on the second restart?
Today for somewhat reason my home PC powered itself down, so when I came back home I had to turn it on, started MEGAsync, it detected the files/folders I modified at work, and after some seconds crashed.
Then I started MEGAsynch again immediately after, this time it didn't crash and it was able, even if with a very slow file scanning, to retrieve back the changes I applied at work to the synced files.
Hi @pidgeon777 , I haven't been able to reproduce the issue, however from the call stack you supplied I may have deduced the problem. Here is an installer with a fix for that, if you wouldn't mind trying it out, and let us know if it fixes the issue: https://mega.nz/folder/VrICQRKA#P26pjQi3T4m_edZ-NA2exA. In case it doesn't, please do capture the call stack again. And, if you can think of any other factors which might be relevant to reproduce the issue such as: number of files/folders in the account, whether you have any outgoing shares or public links, whether changes occurred within those shares or links, and what type of changes, whether you have any special exclusion rules set up for your syncs, or anything else that might have been manually adjusted since initial install and sync setup, please let me know. But, hopefully this installer will do the trick. thanks
Hello,
I faced the same issue. Nothing special about the configuration. Several thousands of files, no public links, no sophisticated exclusions, simple sync scenario with incremental file changes between three computers without conflicts mostly. It worked OK several month before and suddenly started to crash on start. Sometimes it crashes for several times in a sequence before it can finally start and do the job.
MEGAprivate ERROR DUMP Application: MEGAsync [64 bit] Hash: 2afcca96e2111137d7b288b8bc24d6c2 Version code: 4308.0 Timestamp: 1606512109946 Module name: MEGAsync.exe Operating system: Windows 10.0.14393 Error info: Unhandled exception 0xC0000005 at 0x126AFC(MEGAsync.exe) Stacktrace: #0 0x126AFC (MEGAsync.exe) #1 0x170EA0 (MEGAsync.exe) #2 0x134918 (MEGAsync.exe) #3 0x12B535 (MEGAsync.exe) #4 0x11959A (MEGAsync.exe) #5 0x1DEADD (MEGAsync.exe) #6 0x20A8C9 (MEGAsync.exe) #7 0x2F1E7 (Qt5Core.dll) #8 0x84D4 (KERNEL32.DLL) #9 0x51791 (ntdll.dll)
MEGAprivate ERROR DUMP Application: MEGAsync [64 bit] Hash: d50bd4826a271a69d1076442a96e44dd Version code: 4308.0 Timestamp: 1606425772295 Module name: MEGAsync.exe Operating system: Windows 10.0.14393 Error info: Unhandled exception 0xC0000005 at 0x126AFC(MEGAsync.exe) Stacktrace: #0 0x126AFC (MEGAsync.exe) #1 0x170EA0 (MEGAsync.exe) #2 0x134918 (MEGAsync.exe) #3 0x12B535 (MEGAsync.exe) #4 0x11959A (MEGAsync.exe) #5 0x1DEADD (MEGAsync.exe) #6 0x20A8C9 (MEGAsync.exe) #7 0x2F1E7 (Qt5Core.dll) #8 0x84D4 (KERNEL32.DLL) #9 0x51791 (ntdll.dll)
MEGAprivate ERROR DUMP Application: MEGAsync [64 bit] Hash: e7a38a35eb31768244c6832f2062d803 Version code: 4308.0 Timestamp: 1606252517143 Module name: MEGAsync.exe Operating system: Windows 10.0.14393 Error info: Unhandled exception 0xC0000005 at 0x126AFC(MEGAsync.exe) Stacktrace: #0 0x126AFC (MEGAsync.exe) #1 0x170EA0 (MEGAsync.exe) #2 0x134918 (MEGAsync.exe) #3 0x12B535 (MEGAsync.exe) #4 0x11959A (MEGAsync.exe) #5 0x1DEADD (MEGAsync.exe) #6 0x20A8C9 (MEGAsync.exe) #7 0x2F1E7 (Qt5Core.dll) #8 0x84D4 (KERNEL32.DLL) #9 0x51791 (ntdll.dll)
Hi @pidgeon777 , I haven't been able to reproduce the issue, however from the call stack you supplied I may have deduced the problem. Here is an installer with a fix for that, if you wouldn't mind trying it out, and let us know if it fixes the issue: https://mega.nz/folder/VrICQRKA#P26pjQi3T4m_edZ-NA2exA. In case it doesn't, please do capture the call stack again. And, if you can think of any other factors which might be relevant to reproduce the issue such as: number of files/folders in the account, whether you have any outgoing shares or public links, whether changes occurred within those shares or links, and what type of changes, whether you have any special exclusion rules set up for your syncs, or anything else that might have been manually adjusted since initial install and sync setup, please let me know. But, hopefully this installer will do the trick. thanks
I'm trying out this new installer on each of my three PCs, I'll report back in a couple of weeks.
Hi @alexmgerasimov , please do try this test installer which contains a fix for the issue, and please confirm if it does fix the issue for you. https://mega.nz/folder/VrICQRKA#P26pjQi3T4m_edZ-NA2exA thanks
Hi @mattw-mega I'm trying this test installer. It seems working for now. I'm going to continue checking for some more time.
Hi @mattw-mega
It has started crashing again today on one of my machines. This time it even doesn't show a "crash screen" with crash information so I don't know how to get it for you. It is just restarting again and again in infinite loop (each restart adds a new icon to tray which remains there until you hover it by mouse). The only way I was able to stop it is using of shutdown option in the task manager.
Hi @alexmgerasimov , thanks very much for the feedback. Actually we had detected a problem with the fix in the meantime, and have another version that should work - please try this one and let us know, it would be great to get confirmation of that second fix: https://mega.nz/folder/R2YGzRzT#6Ri0MCiLQNDhriLd-BHN3A thanks
Hi @mattw-mega
I'm going to try this new build and will get back to you after a while.
Hi @pidgeon777 , I haven't been able to reproduce the issue, however from the call stack you supplied I may have deduced the problem. Here is an installer with a fix for that, if you wouldn't mind trying it out, and let us know if it fixes the issue: https://mega.nz/folder/VrICQRKA#P26pjQi3T4m_edZ-NA2exA. In case it doesn't, please do capture the call stack again. And, if you can think of any other factors which might be relevant to reproduce the issue such as: number of files/folders in the account, whether you have any outgoing shares or public links, whether changes occurred within those shares or links, and what type of changes, whether you have any special exclusion rules set up for your syncs, or anything else that might have been manually adjusted since initial install and sync setup, please let me know. But, hopefully this installer will do the trick. thanks
So far, so good. That seems to have fixed it.
@pidgeon777 thank you very much for the feedback. I think we will be including this fix in the next release. thanks
Hi @mattw-mega
It seems to work. Thanks for the fix! Will this custom version be updated automatically when you release a new regular version? Or should I update it manually?
Hi @alexmgerasimov , thanks very much for confirming that. The test version will update automatically if you leave that enabled in the settings dialog, when the new version 4.3.9 auto update is released. It'll be first made available as a download from the website, in case you want to install direct from there, to be using the official release (please check for that next week) - however the one you're running is equivalent. thanks
Hello. This is still a very big issue in 2024. I have emulator saves that I would like to sync to the cloud, but every time I add those folders it will crash. I am uninstalling right now, and will come back here to update this if it fails again. Thank you.
Hello. This is still a very big issue in 2024. I have emulator saves that I would like to sync to the cloud, but every time I add those folders it will crash. I am uninstalling right now, and will come back here to update this if it fails again. Thank you.
Back again. This is still an issue after uninstalling, restarting, and then installing the newest version. It specifically happens with my PCSX2 folder. No error, just IMMEDIATE crash. So, even if I want to make MEGA not sync that folder for now, I can't even start the program long enough to make it not sync....
Hello. This is still a very big issue in 2024. I have emulator saves that I would like to sync to the cloud, but every time I add those folders it will crash. I am uninstalling right now, and will come back here to update this if it fails again. Thank you.
Back again. This is still an issue after uninstalling, restarting, and then installing the newest version. It specifically happens with my PCSX2 folder. No error, just IMMEDIATE crash. So, even if I want to make MEGA not sync that folder for now, I can't even start the program long enough to make it not sync....
Try moving the folder elsewhere, so the app will instead error on it, then put the folder back, and make sure it's disabled in the app or delete the sync job.
Hello. This is still a very big issue in 2024. I have emulator saves that I would like to sync to the cloud, but every time I add those folders it will crash. I am uninstalling right now, and will come back here to update this if it fails again. Thank you.
Back again. This is still an issue after uninstalling, restarting, and then installing the newest version. It specifically happens with my PCSX2 folder. No error, just IMMEDIATE crash. So, even if I want to make MEGA not sync that folder for now, I can't even start the program long enough to make it not sync....
Try moving the folder elsewhere, so the app will instead error on it, then put the folder back, and make sure it's disabled in the app or delete the sync job.
Hello! I did this also, but still no dice.
Also, deleting the folder on the cloud, and re-adding the the sync folder again worked for just a little bit and crashed again. I just don't get it. Why is there no error or anything? Just crashes? That's pretty stupid, honestly.
Hello. This is still a very big issue in 2024. I have emulator saves that I would like to sync to the cloud, but every time I add those folders it will crash. I am uninstalling right now, and will come back here to update this if it fails again. Thank you.
Back again. This is still an issue after uninstalling, restarting, and then installing the newest version. It specifically happens with my PCSX2 folder. No error, just IMMEDIATE crash. So, even if I want to make MEGA not sync that folder for now, I can't even start the program long enough to make it not sync....
Try moving the folder elsewhere, so the app will instead error on it, then put the folder back, and make sure it's disabled in the app or delete the sync job.
Hello! I did this also, but still no dice.
Also, deleting the folder on the cloud, and re-adding the the sync folder again worked for just a little bit and crashed again. I just don't get it. Why is there no error or anything? Just crashes? That's pretty stupid, honestly.
Hello! I was able to bypass the stupidity of the MegaSync app crashing on this ONE folder by going to the Mega website and uploading the files from my browser. Stupid to have to do that, but screw it. Hopefully this can help anyone else having this issue! Cheers!