Application reload

I have been using Unity since 2014. I never encountered this issue.

While working, making code changes, saving and coming back to Unity more often I get application.reload message box which is fine as long as it goes away, it remains forever till I end task Unity in Windows using the task manager.

The earlier experience was so much better.

Moreover, many other message boxes keep coming like refreshing scenes etc sometimes even when the play mode is on and for a few seconds they appear and go away.

Application.reload causes a major issue while debugging.

How to reproduce:

1. Star debug mode.
2. Start going through the lines step by step
3. For some reason you want to go back to Unity to check visual states of any game objects you are stuck application. reload appears and you have to stop the debugger. Hence I can no longer debug now.

The application.reload sometimes appear while hitting play mode and this is more dangerous it never goes away till I end task as I said earlier.

I am clueless. Is this a bug or some setting which I need to take care of?

I have already disabled Auto-refresh in preferences settings.

Please help.

 

Thanks MartinTilo for the response.

There is no breakpoint I am sure. To me this is an issue linked with a larger issue of resetting static variables [Domain reload]. Irrespective of the domain reload being enabled or disabled every now and then when I make a code change and run, the application.reload appears and everything is freezed, till I end task and restart Unity, make a code change, test - freeze- end task - restart Unity.

As per Unity docs https://docs.unity3d.com/Manual/DomainReloading.html

I need to reset static vars using the RuntimeInitializeOnLoadMethod, My only problem is I have quite a few static vars and the 3rd party framework I am using has quite a few too. Should I be using this method to find each and every static var and reset?

 

Just to be sure before I raise the bug, can you please elaborate what you mean by "you have your IDe attached".

What I can definitely tell you is the Unity editor freezes with application.reload popup infinitely till I end task. Even when I have not attached any debugger or even when I am not in debug mode.

 

I did what you said and I see no different results.

I have started a brand new project in Unity now and using the same 3rd party frameworks.

The frameworks create voice and video sharing sessions, When I start a session and during testing, if the session doesn't get closed properly because I am still developing, Unity editor freezes again and I have to end task and restart.
So which means its definitely to do with static vars resetting, my only concern is Unity should be resetting those once I hit stop play button in the editor.

Not sure why Unity is unable to do it.

Hence now during development, I have added a button to close the session forcefully, whenever I close the session before stopping play in editor everything is bliss. If by any chance I stop play without closing the session the same error.

I am detailing it out so that it helps you. Really appreciate your time.

 

Ok, I will file a bug report.

 

Bump, this started occurring around the same time as the poster, currently 2020.2.2f1 and Rider 2020.3

When switching Unity to debug mode, then within Rider, attach the debugger to the editor. Now go back to Unity and enter play mode. It will sit at "Application.Reload" indefinitely. This happens across multiple unity projects and even new blank projects.

I don't know if it is a Rider issue or a Unity issue, or possibly a PC configuration issue (similar to how Unity fails to run or has trouble compiling code & shaders if connected to a VPN, though in this case I am not).

It seemed to show up in the late 2020.1 or early 2020.2 cycle

@LeonhardP @MartinTilo

There is also more reports of it here around the same timeframe: https://answers.unity.com/questions/1763357/unity-editor-infinite-applicationreload-when-debug.html

 

I use Visual Studio 2019 and Unity 2020.2.1f1 and I have this problem quite frequently.

 

I too see this problem constantly over the last few months ( currently using 2020.1.15f1 ). Constant meaning more than 90% of the time I attempt to debug a script

Attaching visual studio 2019 to unity to debug, with 0 or more breakpoints, results in unity hanging indefinitely after pressing the play button, until I press stop and detach the VS2019 debugger, at which point unity then launches the game, or starts responding again.

The 'hold on' message that is busy indefinitely is one of the three below:
EditorApplication.playModeStateChanged
Application.Message
Application.Reload

Occasionally, i also see no 'hold on' message, and unity just becomes unresponsive - this happens after a few failed attempts to attach the debugger and launch the game, and quite often when attempting to attach to an already running game in editor. The only remedy to this is to shutdown / restart unity & VS2019, at which point the issue returns to indefinitely hanging on the 'hold on' messages.

In all cases, i see high CPU usage in unity and visual studio 2019, and letting it work for several minutes doesnt appear to improve the situation.

 

same here :/ Unity 2020.3.0f1 with VS 16.9.1

 

Also seeing this with 2019.4 versions of unity and 2018.3.5 version of Rider. I was thinking it was maybe the Rider Plugin being so old, but today I upgraded Rider to the latest version (2021.1) and Unity is 2020.3.2f and the problem is worse than ever.

 

Happens to me too. Hope this gets fixed ASAP. I basically have to restart my PC whenever this happens.

 

It's happening to me too. I run the program few times, makes changes in the code and then the Application.Reload starts and never ends.

 

It's happening to me too. 2020.3.3. It is somehow linked to me starting a thread. Here's the flow that creates the issue:

- click button
- thread starts for open file dialog (StandAloneFileBrowser)
- select file
- abort thread

I can do this as many times as I like in the same 'play' session. When I stop the game and try to start again, I get the 'Application.Reload' that never ends. I have to use the task manager to regain control.

I recently added the 'abort thread' line in the code to see if that made a difference. It does not.

I tried it with the VS 2019 IDE attached and with it not attached. No difference.

If I don't create the thread, everything is happy and I can restart.

This one has me stumped.

 

Any follow up on that? It happens with both 2020.3.5f1 LTS and 2021.1.4f1

I've downloaded the latest version to date

 

Bump, still happening in 2021.1.5f1

 

I'm having the same problem, except mine is easier to reproduce:

1. Click the play icon

That's it. No debugger is attached. I just started Visual Studio, but didn't do anything. "Hold on" window is just showing "Application.Reload" forever

 

I use the Unity2020.3.7f1 without opening any IDE.Clicked the play icon, then "Application.Reload" forever.

 

I've created a bug report for a similar issue I have, while referencing this post:
FogBugz (unity3d.com)

 

This is driving me crazy. I switch from 2020.1.17 (where it did not occur) to 2021.1.7 and I am loosing so much time because of this. I found that changing window focus sometimes causes Unity to continue. I can also confirm that having Rider attached in debug mode will cause a huge delay and the MOMENT I press the stop/detach button in Rider Unity continues, it did not stop at a breakpoint nor was it in pause mode.

 

@MartinTilo , I got a fairly minimal repro project for Editor freeze (tested in versions from 2021.1.3 up to 2021.1.9).

You can find the source code here:
https://github.com/coder89/arfoundation-mock

Simply clone the repo, open SampleScene and enter Play Mode. You should see some red background and some dummy planes moving. Then exit and re-enter Play Mode without doing anything else. Editor will go into infinite Application.Reload state. The only way to stop it is to kill Unity Editor.

From my small investigations here is what is causing it...
SimulateOcclusion.material accepts dummy shader/material that one can use to simulate rendering of camera.occlusion textures on the dummy AR scene. This mono behavior script is attached to AR Mock/Mock Camera game object. Simply removing that material resolves the problem.

Changing Domain Reload flag in Editor settings makes no difference.

Short code structure description: SimulateOcclusion.material is used directly by XRCameraSubsystem.cameraMaterial (or it's fake UnityXRMockCameraSubsystem implementation provided in this project). This material is then used by ARCameraBackground mono behavior (part of AR Foundation) which is attacked to AR Camera game object.

Hopefully this is helpful for finding the root cause of this issue as it seems to be affecting a lot of developers for moths now and it looks like it still isn't fixed.

EDIT:
Bug report: https://fogbugz.unity3d.com/default.asp?1339670_usufrhv3m4it0fi9

 

Same here. It's starting impossible to work at all with this bug.

In my case this issue occurs due to AR Foundation Remote asset. Works fine without it.

 

I also removed multiple packages now like 2d sprite, cinemachine and some more and it becomes quite bearable actually. Still not good but I can work again. These packages should have no effect on domain reload should they? They are forever unchanged once compiled since they are packages and not in my project.

 

Those who are affected please vote here:
https://issuetracker.unity3d.com/is...play-mode-caused-by-arcamerabackground-shader

 

we are experiencing the same issue. We are currently upgrading our project from 2019LTS to 2020LTS. Issue does not come up in 2019 but in all versions that we tested from the 2020 lifecycle. New projects do not seem to show this behavior but I am not sure about that (only tested a new empty project with nothing in it). This issue makes developing in unity basically impossible for existing projects.

 

Hey, one thing that seems to have solved it for us is to set unity to only recompile AFTER you stop play mode. Using 2020.3.4f currently. I can't remember the last time it crashed in a relatively new project, but our old project also made a huge difference.

Edit > Preferences > General > Script Changes While Playing: "Recompile After Finished Playing"

 

Tried that, doesn't help for my repro project/steps.

 

I have a similar issue but only if I use my project with Raider 2021.1.3 (I'm using Unity 2020.1.15f1). if I use visual studio as my IDE I don't have this problem.

PD:With Rider sometimes it get stuck even without being in debug, just by doing a change in the code. I need to kill Unity with task manager and sometimes it even resets my layout when I restart.

 

I got this reload problem just because of PlasticSCM. It's working well without it. The first time to play, no problem. For the second time, 100% I will get an infinite application. reload.

 

Unity folks just closed the bug I reported on this as "Duplicate" but the previously reported bug has less votes. Therefore, asking everyone who's affected by this to upvote this one now:
https://issuetracker.unity3d.com/issues/commandbuffer-native-plugin-events-hang-in-the-editor

@HeiBaiJie, @darkyer, @frankcarey, @jnroesch, @ImpossibleRobert, @Azirell, @v-strelchenko, @jykgod, @Adagio-81, @GilJoWal, @slider115, @superbybot_unity, @hummlj, @RandomProgrammerPerson, @MartinTilo, @BNJMO, @XRA, @LeonhardP , @Zaskar7777

 

ARFoundation (ARCameraBackground) uses GL.IssuePluginEvent so suggected workaround is not possible without creating a custom camera background renderer.

 

Set

 

Following up. Was there any resolution for this?

My recreation steps are the same as this although i am not using PlasticSCM...

 

In our case we used HttpClient.Dispose() in an c# deconstructor. This caused the infinite Reload the second time we hit play in the editor. Very random, but removing that line fixed it

 

That has sped up my Unity immensely, thanks! It was previously taking at least 5-10 seconds, often more like 30 seconds to restart a scene...now it is instant!

 

I get this issue, and after trying the enter play mode settings, I can run easily but at end it will try to reload.

I manage to crash the program and get an error:
Cannot connect to Unity Package Manager local server [Unknown]

from: UnityEditor.EditorApplication:Internal_CallUpdateFunctions ()

 

I have the same issue, at start debuging unity frezze with the "Application.Reload". A light solution is to avoid it using "Attach to Unity and play" instead of just "Attach to Unity".

 

2022 latest version of unity and still getting this bug.

 

And then to pour salt in the wound, when you kill Unity from the taskmanager because it will never complete, I'll get this error and the only thing that fixes it is restarting windows:

 

The "Application.Reload" Happens once a day for me and since it forces me to restart because of the AssetImportWorker0 popup and I'm using 2020.3.31f1. This is getting extremely frustrating.

Every time there is a new Unity version i pray you guys have fixed this issue but it's still there.

Please, prioritize and fix this bug since it COMPLETLY kills your flow.

 

debugging works for me like 1 out of 20 times, otherwise its just stuck.. how was this still not fixed in two+ years... omg

 

Just happened to me in 2021.1.20f1. At the very least, we need more information. "Application.Reload" doesn't leave us a lol to go on in terms of what is going wrong.