No tips for a solution but you can for instance try to find out more looking through the systemlog.
Some commands to start out with, the command below will list all journal entries from the current session, then pipe it into grep en select only the lines with gnome-shell and then pipe those into grep to select only the lines with extension This might give some clues into what is causing this behavior.
journalctl --boot -0 | grep gnome-shell | grep extension
Maybe the locking triggers something else, the command below lists all the errors in the log from the current session, those might give some clues what is happening.
journalctl --boot -0 --priority=err
Please see How to provide good information. I do not agree this is the same problem, it is a different use case and @fselcukcan reports it is solved on his end so it might be better to provide info on your system, preferably with some logging so users can try to help you fix this issue in a new post and refer to this one.