This issue is resolved in VMware NSX for vSphere 6.4.5.
Workaround:
To work around this issue, file a Support Request with VMware Support and note this Knowledge Base article (54442) in the problem description and upload the NSX Manager diagnostic information.
For more information, see: