I have added the potential fix to issue #290. Could you please confirm whether this solves the issue @jwilkes