In Java, is there a legitimate reason to call a non-final method from a class constructor?

Question

I recently spent quite a few minutes debugging a problem in production code that in the end turned out to be caused by a class calling an abstract method in its constructor,

Answer 1

Nice question. I vote "no" and will attempt to incorporate this into my future code. I would think it would be really bad form / risky to call an abstract method.