Thanks, the problem was found and fixed. Please contact [email protected] to get a new build with the fix. This issue will be listed in the release notes for the upcoming 11.2.0 version.