You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Fred Krone (JIRA)" <ji...@apache.org> on 2017/06/15 20:40:00 UTC

[jira] [Updated] (GEODE-1297) use EntryEventImpl.deserializeOffHeap

     [ https://issues.apache.org/jira/browse/GEODE-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fred Krone updated GEODE-1297:
------------------------------
    Labels: offheap  (was: )

> use EntryEventImpl.deserializeOffHeap
> -------------------------------------
>
>                 Key: GEODE-1297
>                 URL: https://issues.apache.org/jira/browse/GEODE-1297
>             Project: Geode
>          Issue Type: Improvement
>          Components: offheap
>            Reporter: Darrel Schneider
>              Labels: offheap
>
> At one point some work was done to allow PdxInstances to be created that would have a reference to off-heap memory instead of copying the off-heap memory to a heap byte array.
> This work was not completed. Currently if you call EntryEventImpl.deserializeOffHeap then it will return an optimized PdxInstance. But the callers need to be changed to then release that PdxInstances off-heap retained reference.
> The main place to look into calling deserializeOffHeap is OffHeapStoredObject.getDeserializedValue(Region, RegionEntry) when it currently does this: EntryEventImpl.deserialize(getRawBytes())



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)