{"id":383329,"date":"2024-09-20T13:45:14","date_gmt":"2024-09-20T13:45:14","guid":{"rendered":"https:\/\/innovationspace.ansys.com\/forum\/forums\/topic\/variables-not-freed-from-memory-after-using-the-clear-script-command\/"},"modified":"2024-09-20T13:45:14","modified_gmt":"2024-09-20T13:45:14","slug":"variables-not-freed-from-memory-after-using-the-clear-script-command","status":"publish","type":"topic","link":"https:\/\/innovationspace.ansys.com\/forum\/forums\/topic\/variables-not-freed-from-memory-after-using-the-clear-script-command\/","title":{"rendered":"Variables not freed from memory after using the clear(); script command"},"content":{"rendered":"

<p>Hi Ansys,<\/p><p>\"image\"<\/p><p>here is the current memory consumption of my lumerical script while running an optimisation using LumOpt (2DvarFDTD). It keeps crashing after only a few iterations and im pretty confident I have a memory leak, but I’m not sure how to fix it. I’ve managed to debug it down to an exact location in the package: lumopt->geometries->geometry.py line 192 <\/p><div><div>Geometry.get_eps_from_index_monitor(sim.fdtd, ‘current_eps_data’)<\/div><div> <\/div><div>which calls the method on line 85 get_eps_from_index_monitor which does the following through the lumapi eval method:<\/div><div> <\/div><div>opt_fields_index_data_set = getresult(‘opt_fields_index’,’index’);<\/div><div>current_eps_data = matrix(length(opt_fields_index_data_set.x), length(opt_fields_index_data_set.y), length(opt_fields_index_data_set.z), length(opt_fields_index_data_set.f), 3);<br>current_eps_data(:, :, :, :, 1) = opt_fields_index_data_set.index_x^2;<br>current_eps_data(:, :, :, :, 2) = opt_fields_index_data_set.index_y^2;<br>current_eps_data(:, :, :, :, 3) = opt_fields_index_data_set.index_z^2;<br>clear(opt_fields_index_data_set);<\/div><div> <\/div><div>If I pause my script just before this part, and directly in the Lumerical console I enter:<\/div><\/div><p>opt_fields_index_data_set = getresult(‘opt_fields_index’,’index’);<\/p><p> <\/p><p>My memory is now:<\/p><p>\"image\"<\/p><p>It increases (my roughly 25MB), which makes sence as we have a new variable storing data, however, if the very next thing I run is:<\/p><p> <\/p><p>clear(opt_fields_index_data_set);<\/p><p> <\/p><p>my memory doesnt change:<\/p><p>\"image\"<\/p><p>whats weird is, if i run the first command again, (remaking the variable), my memory goes up more:<\/p><p> <\/p><p>\"image\"<\/p><p> <\/p><p>and by roughly the same amount, which implies that the original variable was not actually freed from memory and the computer has just allocated a different address space for the “new” variable. F<span data-teams=”true”><span class=”ui-provider a b c d e f g h i j k l m n o p q r s t u v w x y z ab ac ae af ag ah ai aj ak” dir=”ltr”>urther, if I repeatedly run the command “opt_fields_index_data_set = getresult(‘opt_fields_index’,’index’);” the memory ticks up by roughly the same amount each time. This happens throughout the whole iteration in LumOpt (once for each parameter), it then runs the forward and adjoint simulations, and in the next iteration it contunes increasing in memory consumption, but from the higher level, which leads to an eventual memory overload and causes the computer to crash…<\/span><\/span><\/p><p>For confirmation, after I run the clear command and try to call the variable again, Lumerical recognises that it has been deleted:<\/p><p> <\/p><p><span class=”fui-Flex ___l13zv30 ftuwxu6 f1qdqbpl fua484e f1o6l1dn fac4klo frp1kbq f12s2122 f19l72ij fcsrh55 frnyhdv fyo61pj f1spqul0 faegybh fkq5uzf f1x4fozf fwl63ro f1npyoe5 f10yrmu1 f1w45tcp f1dqeblh f18c6rdl f1e7lo8u f1dpi1ry f1vs2jsm f1o6uux1 f1nu0r7q fg0t3io ff98at f2yyzyc f1sjbqdg fyzb71r fh1aahx f1oktu5 f1d3652t fed2bxt ff3017q f1e76dpb f1lwmlrd fgtcxse f1d705n1 f1jrvuk2 f11h0gum f1tandro fxjdbx7 f1hva1tl fsaoqmu f1w7c29l f1uakdsb f7jsfu7 f1hz9qas f1vmprsu f1wogq95 f1oojlmx fpbf6y8 fy6vjqu fuo4419 fbzygsp fnuenae fw75flx f12oply1 fvyt4us f4ki1i fyy2ueq f1w3oopj fum67ou f1j64hbx f1807z01 f1q6iyvy f1wk7p4c f920ium fhj6euq f30elfj f1kcike0 f1byno2r f5wk2nc”>\"image\"<\/span><\/p><p><span data-teams=”true”><span class=”ui-provider a b c d e f g h i j k l m n o p q r s t u v w x y z ab ac ae af ag ah ai aj ak” dir=”ltr”> This effect happens regardless of if I save all the simulations or not during the iteration process.<\/span><\/span><\/p><p>Any ideas on how to actually clear the variable from memory?<\/p><p> <\/p><p>p.s. I am using version 2024 R1 on Windows 11 64 bit<\/p><p><span data-teams=”true”><span class=”ui-provider a b c d e f g h i j k l m n o p q r s t u v w x y z ab ac ae af ag ah ai aj ak” dir=”ltr”> <\/span><\/span><\/p><\/p>\n","protected":false},"template":"","class_list":["post-383329","topic","type-topic","status-publish","hentry","topic-tag-computer-memory","topic-tag-lumerical","topic-tag-lumopt-1"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t