image width and length in train&eval&mesh

Can the param img_wh in train be different from img_wh in in eval&mesh ?
There is "killed" problem when i set the img_wh to (4032, 3024), and it seems to be OOM.

Start by tracing where img_wh is consumed during train, eval, and mesh workflows, then investigate the reported killed process at (4032, 3024). Determine whether training and evaluation can use different dimensions and whether the high-resolution setting causes an out-of-memory failure.

Written by the indexing model from the issue text.