BuildPlayer is fast, or slow, or hangs, or crashes, or hangs for an hour then crashes

Unity Engine
,
1

I just want to know if my team is alone or if everyone else just isn’t complaining.

I just now went through a cycle of BuildPlayer, wait, wait, wait, force-quit, sigh, repeat*3. Previous time I tried to create the .xcodeproj, it worked fine and took 5 minutes. Time before that hung for 15 minutes then crashed twice before the third attempt worked. This time it hung on building the same scene for 30 minutes each attempt until I force-quitted, 3 times. On the fourth attempt, it blew right through and finished the build in 3 minutes.

It’s been like this since we started using Unity with the 5 betas. We’ve stopped sending bug reports for it because they don’t go anywhere. We have our Jenkins job is set up to retry every build 3 times before reporting a problem because it is fully expected to screw up several times before it works.

Seriously. Are there a lot of people working with Unity mobile who are silently living with this? Or is there some evil random problem generator hiding in just our project?

Hey look: It crashed again while I was typing! :frowning:

1 Like
2

and again

3
4

Spent the whole day yesterday watching BuildPlayer fail in new and exciting ways. Different crashes (and hangs) in completely different parts of Unity each time. Everybody else here is working fine?

5

Only common theme seems to be problems with the heap/garbage collector.

6

Can you submit a bug report with one or more of these crash dumps? This certainly looks like something our Editor team should investigate.

7

Was a workaround/fix ever found for this? I’m getting similar issues (100% crash when trying to create a build). I submitted a bug, 730538 via the bug reporter over 2 weeks ago, but haven’t heard back from QA yet, which is quite unusual (usually they respond with a few days at most). I can repro the issue on every version from 5.1.3f1, and perhaps earlier, though I’ve not tried.

8

@pixelballoon

I’ve pinged our QA team, they are going to take a look at this bug report now. Thanks for submitting it.

1 Like
9

Any news on the fix for this bug?

10

It looks like our QA team could no longer reproduce the issue in Unity 5.3. If you are still experiencing it, please submit a new bug report. Thanks!