Apart from web workers and background tasks that run as web workers, all JavaScript code in a Windows Store app runs on what we call the UI thread. That code can invoke asynchronous WinRT APIs that perform their operations on separate threads, but there's one very important characteristic to remember: the results from all those non-UI threads eventually come back to the UI thread for processing. This means that making a bunch of async WinRT calls (like HTTP requests) all at once can potentially overload the UI thread if their results all come back at around the same time. Furthermore, if you (or WinJS) add elements to the DOM or change styles that trigger a layout pass on the UI thread, there's even more work that's competing for CPU resources . As a result, your app can become sluggish and unresponsive.


I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.

This article is related to

C#,.NET,Architect,Intermediate,VS2010,.Net,Articles,Computer Tutorials, Web Development, Web, Javascript