# Memory Leak Issue with ff-mpirun

**URL:** https://community.freefem.org/t/memory-leak-issue-with-ff-mpirun/2369
**Category:** General Discussion
**Created:** [March 31, 2023, 8:36am UTC](https://community.freefem.org/t/memory-leak-issue-with-ff-mpirun/2369 "2023-03-31T08:36:48Z")
**Posts on this page:** 1
**Page:** 2

<div class="post-metadata">

### Author: ![marchywka](https://avatars.discourse-cdn.com/v4/letter/m/ee59a6/32.png) [@marchywka](https://community.freefem.org/u/marchywka)
#### Post date: [April 6, 2023, 3:23pm UTC](https://community.freefem.org/t/memory-leak-issue-with-ff-mpirun/2369/21 "2023-04-06T15:23:19Z")

</div>

I’m not sure what you ultimately want to do but its quite common to start with  
a simple tractable system so you can compare exact and numerical results.  
The FE code isn’t magic, you can compare the Simpson results to the  
PO elements maybe.

I don’t know what kind of code FF actually generates and how slow it is  
vs modern FPU exception handling, probably including div by zero ,  
but the latter can be very slow. I couple  
decades ago, we had some audio code that had to work in real time  
and it generally did well but stopped keeping up ( 8jhz sample rate lol with  
an ACELP decoder and maybe a high-order elliptic filter ). IIRC, the problem  
was feeding the FPU denomral numbers. Checking the intel data books  
these don’t seem to be handled too quickly 🙂

[https://en.wikipedia.org/wiki/Kernel\_(image\_processing)](https://en.wikipedia.org/wiki/Kernel_(image_processing))

[Previous page](https://community.freefem.org/t/memory-leak-issue-with-ff-mpirun/2369.md?page=1)