Skip to main content

Respondus Lockdown Browser - iPad Freezing/Frozen

Troubleshoot Respondus LockDown Browser freezing issues on iPad when used with ALEKS.

Tags

What Respondus interprets as a freeze in LockDown Browser is typically caused by one of the following: 

  • a dialog box from other applications running in the background underneath the secure LockDown Browser layer (students should shut down all other running applications before using LockDown Browser.)

  • corrupted or blocked web links that instructors put in the quiz questions. Navigating to these pages can occasionally result in problems due to problematic content on the page (instructors should test these pages in LDB before opening the exam to students)

  • poor/broken connectivity to the LMS server (usually caused by a poor WiFi connection)

  • load issues on the network being used, or with the LMS server itself. (due to access points being overloaded)

The last two are by far the most common explanations. Should this occur, a helpful article from the respondus website is here: https://support.respondus.com/hc/en-us/articles/4409607186203-LockDown-Browser-froze-during-a-test-and-I-cannot-exit-


In most cases, you can leave the exam, shut down LockDown Browser, restore the internet connection, and then return to the exam (assuming the LMS server permits the return.) Most LMS servers have auto-saving of answers, so they should be able to pick up right where they left off. Keep in mind that if Monitor is required for the exam, you will need to again navigate the pre-exam webcam check....and then the exam should begin where they left off.

Respondus Installation Instructions: https://mhedu.force.com/aleks/s/article/Respondus-LockDown-Browser-Information-and-Troubleshooting

Additional Student Troubleshooting pages from Respondus: https://support.respondus.com/hc/en-us/sections/4409607115931-Student-Support

Additional Respondus troubleshooting instructions: https://mhedu.force.com/aleks/s/article/Respondus-LockDown-Browser-Information-and-Troubleshooting

Top