[User Report] AggregateException

[ShepsyDev]

System.AggregateException: A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property. As a result, the unobserved exception was rethrown by the finalizer thread. (Only part of a ReadProcessMemory or WriteProcessMemory request was completed.)
---> System.ComponentModel.Win32Exception (299): Only part of a ReadProcessMemory or WriteProcessMemory request was completed.
at System.Diagnostics.NtProcessManager.GetModules(Int32 processId, Boolean firstModuleOnly)
at Daybreak.Services.ApplicationLauncher.ApplicationLauncher.GetLoadedModules(GuildWarsApplicationLaunchContext guildWarsApplicationLaunchContext)+MoveNext()
at System.Collections.Generic.List1.AddRange(IEnumerable1 collection)
at Daybreak.Services.ApplicationLauncher.ApplicationLauncher.CheckMods(GuildWarsApplicationLaunchContext guildWarsApplicationLaunchContext, CancellationToken cancellationToken)
at Daybreak.Views.LauncherView.CheckModsToReapply(LauncherViewContext launcherViewContext, GuildWarsApplicationLaunchContext appContext, CancellationToken cancellationToken)
at Daybreak.Views.LauncherView.CheckGameState(LauncherViewContext launcherViewContext, Boolean isSelected, CancellationToken cancellationToken)
--- End of inner exception stack trace ---

[AlexMacocian]

Thanks for the report. Afaik there's 2 scenarios where this happens:

1. The game runs with different permissions than Daybreak. As in, the game runs with Administrator rights while Daybreak doesn't.
2. A race condition where the game process was closing while Daybreak was trying to read its loaded modules.

I should probably handle the first case better. For the second, I don't think there's a way to handle that race condition, because Daybreak doesn't control the flow of the Guild Wars process