A memory leak is when the application keeps data in memory after it is no longer needed. In the browser UI, that usually means something still holds a reference to objects, DOM nodes, or subscriptions after a component is removed or a screen is closed—via closures, DOM references, or failing to clean up event listeners and subscriptions.
When a custom endpoint serves data over HTTP, two levers cut cost independently:
The options-datasource element loads dropdown options for Select and Combobox from a Data Server query or Request Server resource.
Use this page when you are shaping client requirements, workshops, or user stories for screens that show large amounts of data or live updates. The goal is to agree upfront what users need to see and how fresh the data must be—so delivery teams can design a fast, supportable solution.
This section looks at how to style the my-button component. It covers the following items:
Large financial applications often surface hundreds of thousands of rows across grids, with continuous real-time updates. The Genesis platform spreads tuning options across grids, communications, and the Data Server. This page summarises the main levers and points to the detailed references.