hi Philip,
it has nothing to do with multi-threading because the browser is javascript thread is just one.. the author of the link you posted also knows it.. but the principle is the same, he achieved using setInterval while my suggestion was setTimeout.
there is a sample I compiled for someone else, maybe it can help you: JS Bin - Collaborative JavaScript Debugging and this is the thread which this code was linked Busy Indicator issues
however, you forgot the most important part of my reply:
its either your code or SAP code.. in order to find out, forget the SAP component in question and just perform your OData call + js operations - Case the browser freezes it's your code. Case not and when you finally assign your data to the viz component it should then hang, it's SAP code.. simple.
have you tested if the issue does not lie within the SAP delivered code (from this viz component you are using) instead of your code?
comment this out:
- var oVizFrame = this.getView().byId("myVizChart");
- oVizFrame.setModel(sap.ui.getCore().AppContext.myModelForVizChart);
case the issue disappears then we know is this vizframe UI5 control that hangs your browser..
Cheers,
Dan.