PSDImporter/SpriteSkin: Crash when exiting a build on Windows

Hi,

We have encountered a problem when using game objects generated with the PSD Importer from a PSB file.
We use them to animate illustrations, the prefabs are loaded using asset bundles.

At runtime, the prefabs are instantiated in a hierarchy of RectTransform to be displayed in our UI (not sure if this is relevant for the crash).
Everything works fine during the lifetime of the application but when we try to exit the application it freezes and must be killed manually.
There is nothing in the log file noting anything went wrong.

Only removing the instantiation of these prefabs in our code prevent the crash from happening.
Note that this only happen on Windows builds, MacOS builds were fine.
I think the crash does not occur when no Animator is attached but it might just occur less.

The instantiated game objects do not need to be displayed when the application is exited for the crash to occur.
As long as it's been instantiated once, the crash will occur, even if the instantiated game objects have been destroyed.

I've already spent quite some time trying to reproduce the problem in a minimal bug report, using the same assets, but without success. The bug seems to only occur in very specific conditions and timing might be a factor. I recently lacked time to investigate further but it looks like some kind of race condition to me.

We're using the latest 2018.3 version.

If you have or need any information, this would be much appreciated.
Thanks in advance.

 

Could you please submit a bug-report as described in this document:
https://unity3d.com/unity/qa/bug-reporting

It's important that you report these issues together with a reproduction project if you want them to get fixed. If you don't do it, it might be a long time until someone else reports them or until Unity Technologies find them.

After you submitted the bug-report, you receive a confirmation email with a bug-report Case number. You can post the Case number (number only, not the link) in this forum thread for Unity staff to pick up, in case they see it.

 

Yes, I'm used to do bug reports and I usually like to make them as small as possible but as I said this one is tricky to reproduce when starting a project from scratch.
I can't just upload our whole project because it would not work outside our work environment (and is quite big anyway).
I started to rework our project, gradually removing stuff while keeping the crash reproductible but it will take me some more time to finish this.

I was mainly posting here to gather information if anyone had the same problem and maybe found a cause or some workaround.

Anyway, thanks for your replies.

 

I think I have the same issue. For the first time ever, someone played my game for over an hour. At that point, 88% of their physical memory was used up. If you and I are getting the same problem, you might also have a memleak.

Anyway, there is a plugin you can get to turn your scene into its own project. Maybe you can do that to submit it? More info here: https://bitbucket.org/Unity-Technologies/repro-project-wizard

Unity Devs: I'm happy to submit my own project with the bug, but my game is NSFW and so are my art assets. They're clothed, but there's nudity under the clothing layers.

 

I'm uploading a project now, but this is taking forever. Literally over an hour. I think it's uploading my 1+ gig library directory with everything. Is there a way to avoid that so this takes less time?

 

Here's the bug: https://fogbugz.unity3d.com/default.asp?1143228_iv66bqa6db0jl4ev

 

I have the same bug in Windows Editor, can you share a workaround please if possible? Thanks

 

Can you tell me how to upload a smaller bug report next time? This literally took 1.5 hours to upload, and I was afraid to use Unity while it was happening, so I lost 1.5 hours of a day doing this. Most of the size was in the Library directory, but if I delete that, I'm pretty sure Unity is just going to recreate it before I submit the bug.

 

I need an ETA of a fix if possible please..

 

This is fixed in 2019.1.0f2 and the new previews

 

No its not fixed. It works in some cases and doesnt in other cases.

 

Any updates regarding this? We're experiencing it in 2018.3.8 and in 2019.1.3 after upgrading.