System Information
Operating system: Darwin-18.6.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 575 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.9.26
Blender Version
Broken: version: 2.80 (sub 69), branch: blender2.7, commit date: 2019-05-18 17:13, hash: rB1fce0460d522
Worked: (optional)
Sigh you should not put invalid. wait and discuss some more until found out bug. I am show you proof. I ask again, again many times. Boolean need to fix code.
Now you see! I told them many times about Blender 2.60a on Boolean is no error everything perfect.
Blender 2.7 and up cause mess up.
Why not get history Blender . org follow Blender 2.60a application for Mac only not use Windows. get download and you will see.
After reproducing the bug, I discovered the error can be resolved if each object (other), is placed slightly differently from each other, so that the vertices, don't align.
While the idea of modifiers is non-destructive workflow, the issue still persists before and after you apply the modification to the object.
A temporary solution would be to recreate the existing object as a NEW mesh, when you apply a boolean, and then link all existing properties to the NEW mesh automatically.
Internally of course, without the user requiring any extra work.
Ultimately though, the issue should be resolved, just as with versions 2.60a and before. :)
Which means, a minor workaround for now, would be scaling each individual object (other), by 1 unit, resolves the issue.
Please leave triaging bugs to developers.
We already have bug reports about boolean failing, an overview of all those bugs is here:
T47030: BMesh booleans (track todo's)
This is a case for which we already have a bug report open.