[Closed] Memory issue with getvert $.mesh

Everytime you call $.mesh, a NEW TriMesh value containing all vertices, faces, edge vis flags, material IDs etc. is allocated in memory. So for 720 vertices, it is equivalent to creating 720 copies of the mesh in memory. Also, MAXScript has only 7.5 MB of Heap Memory allocated by default, so it will run out of memory much earlier than Max itself – if you would copy a mesh 720 times in the scene, it would still eat a lot of memory, but it doesn’t have as much limitations… You can increase the MAXScript Memory in the Customize>Preferemces>MAXScript tab to avoid memory crashes when collecting a lot of values in arrays and so on.

But back to your problem.
The correct way to do this is to say:

theMesh = $.mesh --creates a TriMesh value in memory with a variable pointing at it
 for v = 1 to theMesh.numverts do 
 (
 theVert = getVert theMesh v  
 --do some more stuff here
 )
 delete theMesh --delete the value, marking the variable as unused for the Garbage Collector

If you want the mesh in world space after all Space Warps, you can use

theMesh = snapshotAsMesh $ --creates a TriMesh value in memory 
 for v = 1 to theMesh.numverts do 
 (
 theVert = getVert theMesh v  
 --do some more stuff here
 )
 delete theMesh --delete the value, marking the variable as unused for the GC