Lukasz Dorau

icon indicating an email [email protected]

icon company Intel icon location Gdansk, Poland

Results 75 comments of Lukasz Dorau

Disjoint pool causes memory leak calling umfMemoryProviderFree() with size equal 0

@vinser52 @igchor The fix is ready: #490 - please review :-)

Get size from tracking provider in proxy_free()

> Do it fix #475 ? > > IF you build umf without tracking provider there is still an issue @lplewa see #485

Get size from tracking provider in proxy_free()

#485 has been merged

merge scalable_pool with UMF

@bratpiorka rebase please

merge scalable_pool with UMF

> > UMF CI fails without TBB now (I think it should not) CI: https://github.com/ldorau/unified-memory-framework/actions/runs/9018809378/job/24780241481 patch: [ldorau@4141a33](https://github.com/ldorau/unified-memory-framework/commit/4141a33f531a2acab83aed202a76f53433a19b44) > > It is OK that these tests will fail - we should...

The proxy library with jemalloc pool can work incorrectly if the app it is loaded for links with libumf.so

Yes, The proxy library with scalable pool works well. Those issues occur only with jemalloc pool, so there can be an issue with jemalloc pool.

Unify licence headers across UMF

I cannot find a link to the Intel guide/wiki, but according to Intel guidelines it should be exactly like in the https://github.com/pmem/pmdk project (do not ask me why ;-)), so:...

Add CMake for examples

@lukaszstolarczuk please verify if https://github.com/oneapi-src/unified-memory-framework/pull/589 fixes this issue

The pool_proxy causes memory leak when used with OS memory provider.

@vinser52 @igchor @bratpiorka > Furthermore, OS memory provider implementation ignores this fact. When 0 is passed as the size argument to the os_free it ignores the error returned by the...

The pool_proxy causes memory leak when used with OS memory provider.

I propose a fix: #482