It depends on the context. Constructor is a method. Every method occupies a space in the memory where it is your code. But I don’t think that’s exactly what he means.
What he probably meant is that the constructor allocates a space in memory to contain the data of the object he is building, and that the method never does this. If this is it, yes, that’s right, at least roughly yes. It can be a little more complex.
If a common method creates a new local object to the method, is it allocating space in memory or not? Indirectly it is. If you find that running a method will never increase the space occupied in the memory is making a mistake. Of course directly the allocation will be being made by a constructor of this object within the method we are talking about.
But we can still do another analysis. The constructor does not allocate anything. Who allocates is the memory manager of the JVM, the constructor only fills this allocated space with data. So strictly speaking, it’s wrong. But you can understand what the statement means, even if it is not needed.
It probably means that constructors create objects and fill them with data (although defaults) and common methods only handle data on existing objects.
Constructors have their own syntax to declare them and to call them.
For being used in the creation of objects exist important implications for inheritance.
See more about the use of builders. When they are called.
Related.
+1 Great question.
– DiegoAugusto