Could you update to the latest stable release and recheck this behavior?
In your old version, device assert might have been missing, which would explain this behavior.
In particular, this was the case in 1.5.0, as device assertions were globally disabled (and fixed in 1.5.1).
I don’t recall, if there were similar issues in 1.4.0.