It’s becoming more and more common that I will go into the Quakity Guardian feature and do two or three patrols, only to be halted. It seems that when I click the button, (yes or no haven’t tried skip) QG freezes up, unabling me to go to the next picture/video. It’s been happening more and more frequently now. http://www.screencast-o-matic.com/watch/cXjo6crRB I use Google Chrome on a Windows 7 laptop. In the video above, I show myself disabling Illyism’s Chrome extension, and clearing the cache. You can’t tell, but I did force refresh as well.

Yeah, my computer occasionally freezes up when I’m patrolling or guarding, so I generally have to click on a link (or failing that, close Internet Explorer) to get out. I just go back to doing it, hoping I can find the instance I was stuck on.

  • one Windows, if it matters

I’ve noticed this happening quite often for me >.<

This is really odd. I have Windows 7 and Google Chrome and tried using Quality Guardian and it worked fine. What version of Google Chrome are you using? Does this also happen on other browsers, or only Chrome? @Cece123 @Tiagoroth To help get the problem fixed, some questions: Can you tell me what browser (and version) and operating system you are using when this happens? Do you have any toolbars or extensions installed?

@Krystle I use the latest version of Chrome, whatever number that is. I haven’t tried it on another browser.

Windows 7, Internet Explorer no toolbars or extensions

I use FF5 Windows 7

I just tested Quality Guardian, it froze, but after a longer time.

@Krystle : I use the latest Firefox on Windows XP. The only add-on is Bloomind FT DeepDark 2 2.3.8, a smooth, dark skin for Firefox.

It seems that now I can’t access Quality Guardian at all.

0_o “This is not the Quality Guardian.” What the…?

Haha, @IShareMahKnowledgeWisely that was me, it didn’t really say that,I put the text in.

Oh. Still, a blank page is still creepy.

@AndrewG1999 Are you still unable to access Quality Guardian?

I added a fix to the QG to address the freezing issue. It should work like awesome now.