DragAndDrop StartDrag consistently failing on Mac

Unity Engine
1

This has halted my work. :frowning: Everything was working fine on Windows, and now that I’ve switched to Mac, my editor extension won’t work at all because of this error:

System info:

  • Mac OS Sierra 10.12.5
  • Unity 5.6.2f1

Things I have tried based on other threads:

  • turn the computer off and on again (workaround recommended by Unity)
  • turn off all Chrome extensions
  • force-quit the pboard process
  • delete the Library folder and reimport everything

None of that has worked. The error happens every time I try to use my custom DragAndDrop code in a custom EditorWindow.

What else can I try?

2

Reproduce it with bare essentials in an empty project? Maybe somebody else on the same version can try it if you also post it or the scripts.

3

I managed to get it to repro with a minimal script. It’s less consistent, but definitely still happening for me very often. Scripts attached.

3150025–239409–CustomWindow.cs (1.5 KB)
3150025–239410–MenuItems.cs (189 Bytes)

4

In case this helps, I also consistently get this error upon closing Unity (these things seem to be related).

3150038--239412--Screen Shot 2017-07-18 at 2.42.25 PM.png

5

I tried it in Unity 2017.1.0f3. When I just do a drag from within the custom window the “dragging a string object” text shows up, following the mouse, but also that error log message on the first drag. After that the message doesn’t repeat. Quitting Unity doesn’t show any fatal errors.

6

I just tried in Unity 2017.2 beta. The dragging works now, but I still get a bunch of console spam with that error. So, better, but still not good. Unity 2017.2b crashed upon exiting from my actual project, but not from a fresh project with these scripts imported, so, maybe unrelated. At least this time there was a Unity bug submit window, whereas 5.6.2f1 didn’t show it on crashing.

7

Yeah, you get spam and I get only one line. Definitely something bigger going on there. File that report and hope they can at least clarify if it’s a Unity bug!