Bug Progressive Lightmapper Crash

Attempting to auto-generate or manually generate any scene with at least one static member with the Progressive Lightmapper results in Unity immediately crashing with a "CPU time limit exceeded" error. Editor.log's last line changes each time, and is usually lightmapper related. The bug has occurred for me 100% of the time over ~15 attempts, even on freshly created projects with a single static member.

I'm using 5.6.0.f1 on two separate computers. One computer is running Debian testing, the other is running Debian Stable. Both have nvidia graphics drivers. Bug happens on both.

Cheers!

 

Issue still occurs in 5.6.0f3

 

Can confirm, this still happens in 5.6.0f3. Here's what my test revealed:
Using Progressive Preview-

• Fresh scene with one cube ( dynamic ), one light ( real-time ), baking doesn't crash Unity.
• Fresh scene with one cube ( static ), one light ( real-time ), baking doesn't crash Unity.
• Fresh scene with one cube ( dynamic ), one light ( baked ), baking doesn't crash Unity.
• Fresh scene with one cube ( static ), one light ( baked ), baking does crash Unity.

http://imgur.com/a/XNNhZ
That's a GIF of my editor crashing, and a screenshot of my Lighting settings.

 

Issue still occurs in 5.6.1f1

 

Can you file a bug report with a project that triggers the crash?

 

Ah! I wasn't aware that the forums weren't the correct method of reporting bugs. Can I get a link to the proper method of filing bugs?

I do see the "Issue Tracker" in the menu, but it doesn't appear to have any method of adding new issues exposed to me.

Cheers!

 

You can report bugs from the "help" menu in Unity ("Help ⇒ Report a Bug...").

 

Oh, interesting. I'd never think to look in the actual software I'm using to file a bug report on it. Shucks, what do you do when it crashes on run? Anyway, thanks Luka.

Report sent, Tak.

Cheers!

 

This bug still exists in Unity 2017.2.0f3 . It was acknowledged in an email, but I'm unsure if it ever showed up in the actual issue tracker.

 

This bug still exists in Unity 2017.3.0f1.

The issue tracker search box does not appear to work on Chrome 62.0.3202.89, 61.0.3163.100, or Firefox 57.0. I tried both signed in and signed out.

It appears that even Unity's bugs have bugs.

 

The search does seem to work fine on mobile firefox. Also, the search box on the page you linked seems to work fine on the browsers I mentioned earlier. Weird.

https://issuetracker.unity3d.com/issues/linux-editor-building-progressive-lightmapper-crashes-unity - This appears to match the Case ID the emails referenced. So I suppose it's actually officially acknowledged? Hurrah! Still continuously broken for six months, though.