PM86071: Memory issues using DataGrids due to editorBehavior
Fixes are available
Closed as program error.
Environment: windows 7 64bit Product name: IBM? Rational? Business Developer Program Version : 8.5.1 Description. Memory issues are observed using DataGrids where when widgets are added and the DataGrid refreshed or resized, after the DataGrid is destroyed a significant number of egl.elements remain. In this scenario creating the DataGrid and destroying it, regardless of the widget used, the number of egl.elements returns to it's initial state. Selecting the resize and,or refresh buttons a few times to then destroy the DataGrid the number of egl.elements does not return to the initial value. This has been identified as an issue with the editorBehavior where Widgets are created but won't be destroyed when the DataGrid has been destroyed because they may be used outside of the DataGrid. The recommendation is for user's to determine when to destroy those widgets by keeping a reference for all the editor behavior widgets to destroy them by demand, rather than destroying them with the DataGrid. Alternatively a new property has been created for the DataGrid by development, manageEditorBehavior, where once this property is set to true all editorBehavior widgets will be managed by EGL so that they will be destroyed together with the DataGrid.
In RBD 8.5.1 and before, when using Datagrid developer has to deal with the widgets created by editorBehaviors when re-render the DataGird.
In RBD 18.104.22.168,9.0 and after, when using DataGrid, developer can set property manageEditorBehavior to yes to automatically manage the lifecycle of the widgets created by editorBehaviors.
Reported component name
RATL BUS DEV
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
RATL BUS DEV
Fixed component ID
Applicable component levels