Runtime Exception in Async Upload Pipeline when starting UWP Debugging

Every time I try to start the debugger in Visual Studio to run a debug build of my game, I get an Access Violation Exception in Texture2D::UpdateFileTextureUploadInstruction(). Here's the stack:

UnityPlayer.dll!Texture2D::UpdateFileTextureUploadInstruction(struct TextureUploadInstruction *,unsigned int)
UnityPlayer.dll!Texture::InitializeFileTextureUploadInstruction(struct TextureUploadInstruction &,unsigned int,bool)
UnityPlayer.dll!AsyncUploadTexture(class Texture &,unsigned int,bool)
UnityPlayer.dll!Texture::BeginAsyncUpload(unsigned int,bool)
UnityPlayer.dll!Texture2D::AwakeFromLoadThreaded(void)
UnityPlayer.dll!PersistentManager:ostReadActivationQueue(int,class TypeTree const *,bool,enum PersistentManager::LockFlags)
UnityPlayer.dll!PersistentManager::ReadAndActivateObjectThreaded(int,struct SerializedObjectIdentifier const &,class SerializedFile *,bool,bool,enum PersistentManager::LockFlags)
UnityPlayer.dll!PersistentManager::LoadFileCompletelyThreaded(class core::basic_string<char,class core::StringStorageDefault<char> > const &,__int64 *,int *,int,enum PersistentManager::LoadFlags,class LoadProgress &,enum PersistentManager::LockFlags)
UnityPlayer.dll!LoadSceneOperation:erform(void)
UnityPlayer.dll!PreloadManager:rocessSingleOperation(void)
UnityPlayer.dll!PreloadManager::Run(void)
UnityPlayer.dll!PreloadManager::Run(void *)
UnityPlayer.dll!Thread::RunThreadWrapper(void *)
kernel32.dll!00007ffa85ab7034()
ntdll.dll!00007ffa864dcec1()

I'm guessing this is part of the Async Upload Pipeline. This happens repeatedly, so I can't just skip it and keep going. The game runs when in release mode, but there are a few some performance issues I need to debug and profile.

Is this a Unity bug or am I configuring something wrong? This is my first UWP project, so I'm admittedly new to these kinds of details. Also, is there a way around this? In my game, the player can essentially see the entire scene when a level loads, so I have very little need of AUP.

Thanks in advance!

 

Interesting...then my issues with connecting the Unity profiler to the Xbox must be some other connection-based problem. I appreciate the clarification on that. At least now I know what to focus on.

There's really nothing in the game's output of any value, unfortunately. It happens before a singe frame is rendered. If you want to research it further, let me know and I'll send you what I can. But if I don't need to actually debug the UWP build in VS to run the profiler, this isn't as high a priority for me.

And as always, thanks for the speedy and helpful response, @Tautvydas-Zilys!

 

Ahhh, Private Networks...of course! Yes, that definitely solved the problem. I got the profiler working.

Some interesting results...all the lag is in VSync calls, and specifically in Gfx.WaitForPresentOnGfxThread. And during some moments (possibly of lower CPU usage) those calls drop dramatically and the game returns to ~60 FPS (from maybe 4 or 5). I don't want to drag this thread outside the scope of the original post, though. I'm sure there are other threads out there, so I'll keep looking. Feels like a solvable problem, though.

I'll make a bug report in Unity, though I've had trouble getting my project uploaded. Something always goes wrong. I'll try trimming some more unused assets...maybe getting the size down will help.

Thanks, again!