Closed pzelasko closed 4 years ago
Does that happen always when you run it? Maybe this is just bad luck, due to some non-deterministic behavior.
I tried this on a Nvidia 1080 Ti with TF 1.15 and cannot reproduce it (I ran it 2 times, and both time were ok). But it might be non-determinstic.
For reference, here it is reported that CUDA 10.0 can have this effect under certain conditions, and it should be fixed with CUDA 10.1.
I'm closing this now, as I cannot reproduce it. Maybe it is due to CUDA 10.0. Thanks anyway for the report.
Setup:
To reproduce:
Possibly the relevant part of the error message:
Full error message: