virtualRowData: if it is an Input in a callback, the memory usage of the website would always go up without collected
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 241
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
@app.callback(
Output("XX", "data"),
Input("ag_grid", "virtualRowData"),
prevent_initial_call=True,
)
def demo(data):
return YY
A small demo to indicate that if putting virtualRowData as Input, the memory usage of the website will always go higher without being collected. ( Assume the ag grid table is updated every 2 seconds)
I know it is not recommend to put it into Input, but sometimes it is useful to do so.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the callback shown in the report, using ag_grid virtualRowData as an Input while the table updates every 2 seconds. Inspect the component behavior during repeated updates and measure whether memory continues to rise. Done means the callback remains usable without unbounded memory growth, with a regression check for this scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100