This error has been there for a while in all my applications. It doesn't seem something you need to worry about. It disappears without changing anything and, probably, it depends on a bug of the NSOpenPanel (I didn't manage to get the same error using the NSSavePanel).
In my opinion, there's no need to investigate further.