Checked the patch, seems to work well.

Note, these edge-cases are detected and handled. there are some cases where exact overlap checks fail - this needs some investigation.

Note, this is caused by the epsilon being measured in different spaces, it's possible for the vertex not to be detected on the face, and the edge not detect intersecting.

T46988 is infact zero area faces, re-opening this one.

@Joshua Leung (aligorith), was also thinking this could be grease-pencil + addon.

Not sure why moving away from an RNA property needs to be slow?

Other engines check DRW_state_is_fbo() before initializing FBO's.

The error is in the polygon, not the OBJ import/export

@John Thomas (m.Th) - this is in fact not an error in booleans, its an error in face-filling.

As @Bob Smith (uvwxyz) said, this isn't a bug. Resulting ngon self intersects.

@Brecht Van Lommel (brecht), good point, either we couldnt access these or the underlying type would need to be exposed.

Corrected rB9a2f7dd77b38504d77b1b058072194496fdc91c9 - BM_verts_calc_rotate_beauty locked rotating out of degenerate cases, causing confusion.

Looks like this is caused by Win32 clamping windows bounds based on the default monitor.

@Patrick Boelens (senshi) in 2.7x this can be done by placing the empty object behind other objects, then toggling xray to render on top.

This is caused by dynamic point doing its own object data updating (BKE_object_modifier_update_subframe) which runs at the same time as the scene_update_object_func task see:

Hah, I see where you're coming from but think you miss that Blender has a history of not treating errors reading corrupt files as bugs. (or only fixing ones that users run into but in general not assuming input is totally broken)

@Emmanuel LORANT (asturias), if you change the layout to be horizontal [1, 2, 3] - does Blender open on the correct screen?

Yep, extern/intern we only touch if they're maintained by blender devs.

Committed fix for one of the CVE's, note that I think we could make the CVE's public. It's no secret that corrupt files can crash Blender in various ways.

Committed fix rB829916f4e57a2d1580ff3b625f6bb909b9144a20

@Sergey Sharybin (sergey), yep, pretty much agree except possibly the conclusion.
Fixing isn't so complicated, I added some bounds checks, then noticed saving wasn't working for a few releases.

@rm beer (rmbeer) - if you can redo this bug, please report a new bug.

@Kenrick (Prototype) - thanks for looking into a fix, however this now works in 2.79.

This is fixed by rB892d304dedb60891d9e0b3091eceecb163644215