When viewing a Change Schedule the browser page freezes upIssue Open a Change Schedule that has a definition that uses a qualification that returns a large number of Change Requests (several hundred). For example: one with the qualification: Active=true.Scroll down through the list of scheduled Change Requests.Eventually, the web page will freeze and possibly not recover.CauseThe "freeze" occurs during the parsing of the Change data in a 3rd party library used by Change Schedules. When the user scrolls down, there's a call to the server to find more Change Requests that meet the filter condition set in the Change Schedule Definition record. The server returns the data in blocks of 20, and the code appends it to a list and passes it to the 3rd party library to parse into a format needed to render the Gantt bars in the calendar display. This parsing is what takes so much time. And the speed is dependent upon the available memory in the instance. This is why the issue is typically reproducible in production instances with a lot of activity, or in non-production instances that do not have the memory required to handle the data processing.ResolutionUnfortunately, there's no easy solution for this, as it involves a library that we cannot change. We would suggest that you modify the filter condition in the Change Schedule Definition so that the number of records retrieved are less than 100 or so. For instance, you could modify it to show "active" changes with a "planned start date" on "This week" or "This month". The purpose of the Change Schedules feature is to highlight any potential conflicts between Change Requests, but if you show hundreds of them, its usefulness is diminished.