http://www.k-wave.org/forum/topic/apparent-memory-leak-in-kwave-11-matlab-2014a Support for the k-Wave MATLAB toolbox en-US Wed, 13 May 2026 01:34:27 +0000 http://bbpress.org/?v=1.0.2 q http://www.k-wave.org/forum/search.php http://www.k-wave.org/forum/topic/apparent-memory-leak-in-kwave-11-matlab-2014a#post-5081 Mon, 11 May 2015 09:41:28 +0000 bencox 5081@http://www.k-wave.org/forum/ <p>Hi vchaplin,</p> <p>We can't immediately think of what's going on here. Would you be able to send us the example you were running so we can try and reproduce it?</p> <p>Thanks,<br /> Ben </p> http://www.k-wave.org/forum/topic/apparent-memory-leak-in-kwave-11-matlab-2014a#post-5061 Wed, 29 Apr 2015 23:05:25 +0000 vchaplin 5061@http://www.k-wave.org/forum/ <p>I'm running a simple 2D simulation using the MATLAB interface, and kspaceFirstOrder2D(), on a brand new PC with 16GB memory. The simulation proceeds correctly but at the last step before the function returns, I believe when the algorithm converts the k-space solution back to the spatial grid, all available memory is quickly gobbled up. Matlab then returns it's boiler-plate out-of-memory message, indicating the problem came during ifft(). There certainly is enough memory to handle the space-time grid and fft. Indeed, I reverted to version 1.0 of k-wave, and everything works well. Additionally puzzling is that if I run the same code on my laptop, with Matlab 2013b and k-wave 1.1, I do not get the same memory usage problem. Any ideas? My PC is a Windows 8.1 Pro, Intel Xeon v3. I don't have my laptop in front of me but is about two years old running Windows 8.1, Intel i7 processor with 8GB memory. </p>