I noticed the same with mesh hair (imported from DAZ studio), I ended up deleting all the faces that are not visible from the outside, then some more and finally I was able to get it to render. Without the hair mesh the freestyle render is so fast I barely notice it.

Indeed seems to be fixed, perhaps due to rB41cb5658803bf3b96f18e93c74c6af66ecdb1e83.

It seems this bug was fixed recently, at least on Linux.
Can someone confirm this?

Jus these things:

Does it print anything suspicious if you run blender with --debug-gpu and render? (So it crashes)

Yes works fine with Cycles, Crashes with Eevee.

i just checked with latest beta and for me freestyle only works, if I select a collection with no sub-collections.
don't know if this is a bug or meant to be, but I would prefer if it could render all sub-collections as freestyle too.

Does it only happen with eevee? Does it crash if you choose cycles instead?

Yep same thing

It renders fine for me:

This is solved in 2.8, where freestyle uses the same triangulation as everywhere else in Blender.

Confirming - got the same issue

Updating blender2.8 -> master in my local repo, and rebuilding, showed the problem is resolved. :)

@Jaggz H (jaggz), rB168a6a4bfc1 is too old.

In 2.80 (git built within the week (168a6a4bfc1)).
Linux (Debian stable).
Official Nvidia drivers. Geforce 970. Driver Version: 390.48

Excellent! You guys are too fast for me. :)

This was just fixed, your build is one day too old.

Confirmed, checking...

@Daniel Oakey (doakey3): my bad [was accidently on an older revision rB7c438e536 to check another report], sorry.

I have tried your file. If I set the collection to "Inclusive", neither cube will be freestyled. If I set it to exclusive, then both cubes will have freestyled edges. The issue I'm having is that I cannot make it so one cube is freestyled and the other not be.

Well, like I said: in the file I posted I cannot reproduce the issue, both inclusive/exclusive collection do work on my side, have you checked that file (if that works for you as well, it gives us a hint on how to proceed)

This bug occurs with both Eevee and cycles.

Cannot really reproduce here.

Thanks, will commit the patch.