Univention Bugzilla – Bug 43375
Firefox hangs after clicking 'finished' in system setup
Last modified: 2019-01-03 07:19:22 CET
After clicking on 'Finish' on the last system-setup page, firefox sometimes does not exit properly, but keeps on running with 100%CPU. stracing the process shows endless calls to ... madvise(0x7fefb5a00000, 15728640, MADV_DONTNEED) = 0 madvise(0x7fefb5a00000, 15728640, MADV_DONTNEED) = 0 ... Always the same address. No swap is used, no messages in dmesg. Also reported by a partner ISV
Sounds a bit like the problems we had at Bug 40985 when calling window.close(). We replaced window.close() then with a UMCP call to setup/closebrowser. However, if this command fails, window.close() is still used as fallback case. In order to better understand what is happening, I would do: * Open the JavaScript console (ctrl + shift + k) before launching the join process and select the network tab of the console. * Create a snapshot after the join process has finished and the final page is shown in the wizard. * Click on "Continue" and see whether the all to setup/closebrowser succeeded. If not we should investigate closer what exactly happened. Breakpoints in the JS code might be helpful, as well: setup.js → lines 264 and 250 (after call to setup/closebrowser) Erik said that he needed to try several times until he managed to reproduce the problem.
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018. Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact your partner or Univention for any questions. If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.