duplicated this behavior also on a XPS 13 equipped with Intel i5 CPU.
Additionally noticed that the error seems to be only happening with API 25 but never happend with API 28.
Could you please try with API 28?
Is anyone else using an API different to 25 and is facing similar issues?
Please be informed that I will not be in office until 23rd of July.
With kind regards,