As I went to confirm that this bug got resolved I found that F12 rendering now doesn't work at all, either with release or debug builds, and regardless of whether Freestyle is enabled or not. This only happens when EEVEE is the active Render engine.

Eeeeh ok, then I guess we can close as solved. :)

@Tamito Kajiyama (kjym3) mind checking on that one? thanks.

I've also noticed that the thing that seriously slows down my code is the OSD mesh creation. On the squirrel (17 106 quads) OSD creation takes 4.346086 sec while the rest of my modifier code takes 3.414331. I'll try to multi thread a part of my code. If that goes well then I might push the time down to around 1 sec for the non OSD creation stuff.

As of Blender 2.8 f08f6c1adec I'm not able to reproduce the above issue anymore (with a release build). Freestyle still doesn't get rendered correctly with EEVEE (F12 render shows a black screen), but I guess that's to be expected at this stage.

@Bastien Montagne (mont29)
This time I even used a debug build, quickly obtaining a crash within 1-2 attempts of rendering the image with Freestyle enabled, as of e91bdb10e9c. Note that it says RX580 but it's actually an RX480 (there should be no difference OpenGL-wise; this is due to a GPU modification).

Could be a lot of things, but would suspect some OpenGL issue… Can you please run it with --debug-gpu option and attach as text file here any error printed out in the console (do not paste it directly in comment)? Thanks. Also maybe worth trying with -t 1 option (to run in single-thread mode).

In T56015#519795, @s12a (s12a) wrote:

What GPU are you using?

It could be a GPU vendor-specific issue. What GPU are you using? I just tried again with the latest buildbot build, and it crashed on the first attempt, by the way.

Can't confirm on Windows 7
Rendered correctly with no crashes 15+ times.
with dc3b3d94538

A quick update. I've worked with the GSoC student YimingWu so see if my work would be useful with his LANPR solution (and it seems to be!).

Freestyle creates a new scene to render lines, which is not the same as the existing scene. In general Blender can have multiple scenes active at the same time.

Animated edge marks could be a partial solution (a workflow in this approach could be tedious and even not applicable in some cases though) -- see https://wiki.blender.org/index.php/User:Kjym3/DevFundProject/InterimReport for more information.

@Tamito Kajiyama (kjym3) Hey, by any chance can you take a look at this? @Zachary1234 (Zachary1234) was asking on IRC today if there is any chance that this could be fixed/improved/a way around the issue. Thanks.

This is a dependency graph issue.

More than a week without reply. Due to the policy of the tracker archiving for until required info/data are provided.

Please always attach a small and simple .blend file to help reproducing the issue.

Hi, this bug seems to have a long history....
You seem to have figured out the underlaying problem down to the last detail. Good work!

Thank you, that certainly seems to fix the issue, although it makes all Renderlayers transparent (which is not the case in Blender Internal, although I'm not sure if that matters :D)... In any case, I guess this is not a real issue and can be closed.

It is not the same bug.
Cycles requires Transparency option enabled under Film panel in Render Tab.

The issue here is not the bevel modifier but just exponential growth. ((You have the horizontal edges (8 * 6 * 16) * subdivisions + other geometry 10 ) = 7680 This number is reported in Blender. You then factor in the modifiers: 7680 * (2 solidify) * (7.3 bevel) * (23.3 subsurf) = 1,794,048 worth of edges for that object (way more than you need, try decrease the subsurf to see if it works) Anyway, no bug here.

Hello, today I downloaded the latest version and the file caused the crash Blender, below the file generated by debugging.

Hello again, I did some tests and verified that the problem of the total drainage of resources and the block of my PC with 4 GB of RAM, occurs only when the active modifier bevel in horizontal bars, none of the other modifiers I take issue, I think the problem is very unusual, as well as being definitely caused by a failure of NPR engine optimization.

OK, I understand well the difference between ram and size, and I understand also that a very small file may generate abnormal memory consumption, but believe me when I tell you that this is an inherent problem with modifiers, and covers even groups and instances, said this today I'll do some tests on a different PC with less RAM,
This is a long period of time I use freestyle to generate 2D views and I use it daily, and I found other problems caused by other problems of various kinds.

File size is not the same as ram.

Hello, I am not very much agree with your assessment, the attached file is only 281KB with some modifiers, and in my case locks the PC, while this sub is a rendering in Freestyle that runs in just over three minutes, and it is more 103MiB

Freestyle is highly un-optimized for me Blender drained 10gb of ram because you only have 4gb it is quite apparent why Blender would hang.

Good morning, I wanted to add some more information.

Hi, I tried again today but to no avail, Blender runs out of resources of my PC, the cursor does not move, nothing works not even the esc key to stop,

Works in Windows 10 home edition. This was on 4.2Ghz 6-core CPU 5820k. Freestyle is single threaded, so it's interesting why your whole computer slowed down.

Fixed in T50995, thanks for the report!

Will have a look.

I tried this on both mac and windows and found it to behave the same.