Script Running Slowly Error in IE

[Eric]

I am trying out the new RadDropdownTree control, but I am getting an error in Internet Explorer.  It says the script on the page is running slowly.  I have tried setting the scriptmanager to release as suggested on this page, but I am still getting the issue.
http://www.telerik.com/help/aspnet-ajax/treeview-troubleshooting-treeview-script-causes-ie-run-slowly.html

[Kate]

Hello Eric,

Can you please provide more details on the scenario that you currently experience? For example providing either a live url or a very simplified runnable project so we can replicate the issue from our side and help you out would be very useful. can you also clarify the exact version of the RadControls that you are using?

Regards,
Kate
Telerik

[Phuc]

I'm getting this issue same when using RadDropDownTree Telerik while Filtering in IE8. How to resolve this issue?

[Phuc]

In Filtering: Big data from >300 rows is appear this error. >2000 rows is RadDropDownTree control don't working.

[Nencho]

Hello Phuc,

The filtering is achieved entirely at client-side, iterating through the entire NodesCollection at each keypress. With such big amount of data, which the RadDropDownTree is supplied with, the javascript execution would be a bit slow. However, in combination with the usage of IE 8, that is not quite fast in terms of javascript execution, this operation will be inevitably slow.

Regards,
Nencho
Telerik

 

 

[Henry]

Try running the page without the debugger attached.    the debugger will slow down raddropdowntree and treeview insanely.  Just open another IE window and paste the url visual studio is using.  This is assuming you are using the debugger and doing development. 

[Sam]

We’re experiencing the same issue, but a little more compounded.
We have some 5000 to 10000 nodes in 2 levels in the tree, it takes a long-long
time to expand, and sometimes we get the IE script issue, and sometimes it just
hangs forever. If the tree is not built for this type of performance, please
let us know and we can represent the data structure in 2 dropdowns, but the
Tree was our preference because it allowed the user to select nodes from
different Parents.

[Nencho]

Hello Sam,

Indeed, when such enormous portion of data is used to databind any control, the browser will hang, as there is a lot of html that needs to be rendered on the page. I would suggest you to use the RadComboBox or the RadAutoCompleteBox, in order to implement the desired functionality.

The RadComboBox has its LoadOnDemand functionality, which can help you achieve the desired scenario, regarding the large portion of data that needs to be used.

• Documentation - http://www.telerik.com/help/aspnet-ajax/combobox-overview.html
• Online demos - http://demos.telerik.com/aspnet-ajax/combobox/examples/overview/defaultcs.aspx

On the other hand the RadAutoCompleteBox relies on callbacks, in order to perform a request to the underlying datasource and return the set of items, which correspond to the typed in the input characters.

• Documentation - http://www.telerik.com/help/aspnet-ajax/autocompletebox-overview.html
• Online demos - http://demos.telerik.com/aspnet-ajax/autocompletebox/examples/default/defaultcs.aspx

Regards,
Nencho
Telerik

 

 

[Sam]

Thank you for the information. The Tree gives us a great
advantage because we can select multiple children from different parent nodes.
Do you think the TreeView is more capable on its own without the Combobox?

[Sam]

After much testing, the answer is NO, the Tree by itself is much faster and handles Java side "stuff" much faster, such as clicking a parent node and having all children nodes checked.

[Robert Schoen]

I am having this issue using 2016.1.113.40.   It recently was discovered after upgrading from IE 9 to IE11.   It also only seem to be an issue while debugging.   Chrome and Firefox does not seem to show the same problem.   I have a tree with about 500 items and about 5 levels. 

Is there any work around for this in debug.

[Nencho]

Hello Robert,

The amount of data that you mentioned  ~ 500 nodes in an hierarchical structure should not impact in such a manner the browse behavior. Could you please submit a support ticket, along with a runnable sample attached so we could inspect your proper implementation locally and pin down the reason for the experienced issue.

Regards,
Nencho
Telerik