On Thu, Feb 11, 2016 at 10:46 AM, Thiago Milanetto Schlittler <
thiago...@gmail.com> wrote:

> Hum … thanks, the error was somewhere else in my code, in a part not
> necessarily linked with libMesh or smart pointers, but using the
> point_locator avoids a memory leak.
>
> Just one thing, if I understood correctly the point_locator() method is
> deprecated. So, it’ll be removed in a future version of libMesh, no?
>

Oops, yes, you should call MeshBase::sub_point_locator() instead, which
does basically the same thing, but ensures you don't build a PointLocator
if you're already in a threaded region.

-- 
John
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to