NullReferenceException about protopromise HOT 10 CLOSED

That's strange. That line is

InternalHelper.PromiseBehaviour.Instance._updateProcessor.WaitFor(ref copy);

Which tells me PromiseBehaviour.Instance is null. That's only nulled out in OnApplicationQuit. I wouldn't expect other async code to continue running after that, but apparently it does.
I only started nulling it for AppDomain reload disabled support (#204). I wonder if there's a way I can keep that alive while still supporting AppDomain reload disabled.

from protopromise.

Another data point: times when the exception doesn't occur, it can take a suspiciously long time for all the images to load...no activity then boom they come in (if they come in). This seems consistent with they are queued under the hood, I exit play mode after seeing no activity for several seconds, and there's the OnApplicationQuit

from protopromise.

It get's weirder -- I'm watching net activity on my machine and it stays pegged up, which I can only presume the image(s) are continuing to fetch. This occurs 14 images in to a 20 URL queue. Confirmed that the activity is this issue since it goes away when I exit Unity.

from protopromise.

Confirmed that the activity is this issue since it goes away when I exit Unity.

Does it behave correctly if you enable AppDomain reload?

from protopromise.

Same behavior if regardless if all 3 checked or not. Restarted Unity a couple times over this and encountered this with all three unchecked.

from protopromise.

Argh, looks it's on me! Had a bug causing reloads to keep going. Sorry brother!

from protopromise.

Should I just use the latest from main? Seeing commits there and happy to help with testing, just want to understand what will be most helpful to you.

from protopromise.

fix-nullref-onapplicationquit branch

from protopromise.

LGTM.

I reintroduced that bug that was causing a non-stop flood of image load reqs and no exceptions thrown on stopping the player.

from protopromise.

@drew-512 Thanks!

from protopromise.