I've hit this issue a few times. I'd also like to know the explanation of this behaviour since it left me completely puzzled.
@nucky9 Thanks for the tip with main proc, it helped me work around this pesky warning. However, I'd still like to know what exactly I did wrong.
