Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Paging Toolbar crashes when creating and destroying Grids too fast. #1835

Open
fabriciomurta opened this issue Oct 29, 2020 · 0 comments
Open

Comments

@fabriciomurta
Copy link
Contributor

Found: 5.2.0
Ext.NET Forum thread: Strange error on component destroy

If repeatedly and quickly a grid panel, using a paging toolbar, is created+destroyed, a race condition may trigger where the paging toolbar tries to load its status when being destroyed.

This happens because, as the store's data is nullified during destruction, a "load" event is triggered in the Paging Toolbar, and it does not check whether the "load" stimulus was actually a null-data-load one.

Probably the best way to avoid this is, to make the paging toolbar load event not be triggered at all when the grid is being destroyed. That is, destroying the paging toolbar before the store is.

Alternatively by at least untying the events before the store is destroyed may allow the race condition not to trigger.

A quick workaround is just check whether the toolbar is destroyed or destroying at the time onLoad is called.

Sencha test case pending: the test case provided in forums is full of unrelated entities to the problem and it needs to be cleaned up before it can be made into a pure Ext JS test case. This issue may be Ext.NET specific as there is an Ext.toolbar.Paging.onLoad override.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant