You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Issues with frozen WIN App and Unresponsive page on WIN Chrome #7911
The huly on Chrome, as well as on the Windows App, has become frozen and unresponsive. It's stuck on the Human Resources page.
However, when I tried accessing the form tablet via Chrome, it is accessible, but the loading speed was very slow.
I can't even sign out from the Windows app, nor can I reload or force reload.
How it started:
I was trying to change the name of the 'Organisation' shown under my name in Human Resources but couldn't find how to do it. I was only able to create a new department.
Then, I was working on my schedule and added a vacation. Since then, the application has been stuck on the same page in the Windows application, and it also appears as an unresponsive page when I log in through the Chrome browser.
Check the screenshot.
Huly-Windows-0.6.423.exe (Windows 10)
Windows Chrome version 132.0.6834.160 (official build) (64-bit)
Android Tablet Chrome latest on 4 Fab 2025
The freeze was caused by an infinite loop in the activity view, which was fixed in #7952 as noted in the thread; the fix is part of the current code. This looks resolved, so the issue could be closed.
@priyank-dxd — based on the check described above, this looks resolved in the current code. Could you please close this issue if you agree? If you think it is not fixed yet, please describe what still goes wrong (steps, expected vs. actual behaviour), so it can be looked at again.
Activity
huly-github-staging commentedon Feb 4, 2025
Connected to Huly®: UBERF-9390
akhismat commentedon Feb 6, 2025
Fix merged
#7952
MichaelUray commentedon Oct 17, 2026
The freeze was caused by an infinite loop in the activity view, which was fixed in #7952 as noted in the thread; the fix is part of the current code. This looks resolved, so the issue could be closed.
MichaelUray commentedon Oct 20, 2026
@priyank-dxd — based on the check described above, this looks resolved in the current code. Could you please close this issue if you agree? If you think it is not fixed yet, please describe what still goes wrong (steps, expected vs. actual behaviour), so it can be looked at again.