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.

I confirmed this is a regression from the 2.76 release. I will look into the issue.

Thanks Bastien for the triage, and I confirmed the issue on my side. I will look into it as soon as time permits.

@Tamito Kajiyama (kjym3) Care to check this one? thanks :)

If I remember correctly, I didn't even consider the possibility of imposing the constraint that there must be at least one lineset. It is easy to check if there's a lineset, and I was not aware of negative effects due to an empty set of linesets.

This issue has been resolved. Thanks for the bug report!

I can confirm the issue. The UI code doesn't have a check for lineset existence, resulting in firing up errors in the console.
@Folkert de Vries (flokkievids) Would you mind take a look? Thanks.