Forum Discussion

Mgamerz's avatar
3 years ago

EA App cloud sync enumerating save directory of games thousands of times

Product: The EA app
Platform:PC
Error Report ID (learn how to create an Error Report ID in the sticky post) 436d04a7-19a7-449f-a57e-98cdf6898538
Which client functionality are you experiencing this bug with? Launch Game
When did this happen? (dd.mm.yy hh:mm) 01.26.22 12:00
Summarize your bug (This is tested against Mass Effect 3 and Mass Effect Legendary Edition). The EA app has forced cloud sync which has terrible performance when a large number (1000+) of save files are encountered - far worse than it should. When looking at the application behavior in ProcMon it is apparent that a huge amount of time is being wasted enumerating the save directory hundreds of thousands of times. Games take so long to run that it appears like the game will never actually launch. With the new forced EA-app that came into effect today, I have seen many of my mod developers (I head the ME scene) seemingly be unable to run their game.
How often does the bug occur? Every time (100%)
Steps: How can we find the bug ourselves? Add a lot of save files to the Mass Effect Legendary Edition saves folder: For example in the modding scene we use this set of save files for each game, labeled (internally) for us to jump to any point in the game. In total this has hundreds of saves. https://me3tweaks.com/permanent/LEDebugSaves.7z These are extracted to: %USERPROFILE%\Documents\BioWare\Mass Effect Legendary Edition\Save - with each archive being extracted into the respective game. The game must have been run at least once.
What happens when the bug occurs? The EA app enumerates the save directory for this game hundreds of thousands of times - essentially running in O(N^2). It takes literally - I'm not even kidding - 5 minutes and 32 seconds for me to run the game. I don't know why it is constantly enumerating the folder list when it seems like it just needs to get a list of files and then cache that into a variable. This current implementation is extremely slow - on the levels of GTA 5 buggy login slow. It is faster when it doesn't have to do a full sync - we're still talking like a minute to launch - but when a save sync occurs (e.g. my other computer generates a new save) it's back to the 5 minutes to run thing again. It really wastes a lot of time, especially for my developers who constantly restart the game.
What do you expect to see? I expect better performance. I don't expect miracles but I also don't expect it to take 6 minutes to compare a local and cloud version of a folder that is not more than a couple of megabytes. At the least, I'd want to see one of three things (preferably all of them): 1. Better performance for sync. Do not enumerate this directory hundreds of thousands of times. 2. Show something to the user that something is happening. The app currently gives you zero indication it's doing anything. 3. Give me the option to turn off cloud sync like we could in Origin. That's why this was never a problem before (it was still a pain in Origin but could be easily circumvented).

Using ProcMon I was able to filter it to all activity by EADesktop.exe. When cloud sync occurs on game launch, you can see it querying the same directory thousands of times for some reason. I know a lot of this internal methods, but this seems far too excessive to be optimal behavior.

16 Replies

  • Same. MELE takes 6 mins to launch, and it doesn't even launch on the first go. Saving also has huge delays for some reason, takes 5 seconds for the menu to pop up in game. :/

    Also, cloud saves won't even sync. I switch a lot between 3 pc's, my office one, my home setup and my steam deck. I basically have to copy a usb all the time and move them around.

    Also, ever since updating to this damn thing, I haven't gotten a single achievement - basically didn't get any for MELE 3

  • We deserve to have a responce from the EA APP DEVELOPERS. when STEAM and the epic games store lets you control cloud saves you know you are lacking in quality fetures.

  • For me, MELE will not open at all.  Just bounces between Launch and Main menus.  Not even trying mods through ME Tweaks, just both basic Steam and EA apps.

    Finally got Andromeda to work, but without mods.

  • I avoided the EA app because Origin ran just fine.  Only when EA actually force-closed (killed) Origin did I start using the app, and as a user, I find it regularly fails to update saves "to the could" from a machine I have hard-wired to my router (so I know the problem isn't here,) and I wasn't doing anything out of the ordinary.  Shouldn't this have been a nothingburger of a transition?  Wouldn't it have been better to leave Origin supported until the app was at least 90% glitch-free?  I haven't gotten my mod to the point where I have to start QCing it (which I expect to take many restarts and saves,) but even as a plain-vanilla gamer with a tendency to second-guess myself, I find the app glitchy and unreliable with the 200-300 saves I have per "career."

    If Mass Effect is supposed to allow for - and encourage - replay, the required overlaying "app" simply cannot be allowed to fail in this way!

  • @rjrosemeyer Have you tried FrostyFix? It got Andromeda running for me, with mods. This link includes directions and a D/L link: github dot com/Dyvinia/FrostyFix
  • I was the same, Origin was a lifesaver for me 90% of the time. I was able to run through various playthroughs of the Mass Effect trilogy with various mods installed, until the EA Desktop app was forced on us.I still can't believe they pushed such a broken app on us, when Origin worked perfectly fine.

    Now I am encountering bugs that simply did not exist before I started using EA Desktop.

    Bug 1, which took me a while to fix, made it so that Mass Effect 1 would boot up but freeze after 2-5 minutes of gameplay, every single time. I fixed this by re-enabling the in-game overlay, which was on at first? I don't know, it was annoying to sort.

    Bug 2, which came about not even a day after I fixed bug 1, completely prevents the game from launching. Every single time I re-install Mass Effect 1 and click play, the splash screen pops up for 1-3 seconds before immediately disappearing with the reappearance of the EA Desktop app, signalling that Mass Effect closed before it launched. This happens 100% of the time, after a dozen reinstalls through both EA Desktop and even the Steam version of Mass Effect 1. The game is literally unplayable on both my gaming PC and gaming laptop, and I have not seen a fix anywhere.

    I just want to be able to keep playing Mass Effect 1, but ever since I was forced to use EA Desktop, it became nearly impossible, especially after I kept struggling with texture mods not working because of something missing. Honestly gets me so angry that there doesn't seem to be a fix for the problem anywhere on the internet.

About EA app Technical Issues & Bugs

Having issues with the EA app? Join us to report bugs, and find help with downloads, DLCs, purchases, and login errors.6,896 PostsLatest Activity: 2 minutes ago