Cantr II Discussion Forum

Not really sure if this is an issue on the end of Cantr or on the end of my browsers, but recently there is a script which from time to time freezes what browser I'm using at that moment.
Sometimes it unfreezes again after a while (from 5 seconds to half a minute so far), sometimes I have to terminate the browser through that thing on the tip of my tongue... the alt-ctrl-del way.
It has occurred while I've used FireFox (my main browser), once with Chrome, and once with Safari.
It's occurred in the past, but only a few times, however it started occurring more often since around the time that FireFox rolled out version 3.6...
I don't remember for certain if the increase in occurrance happened just before I updated FireFox to 3.6 or just after, but in FireFox I managed to see that the script in question is prototype.js, it either stops working or goes off trying to build the great wall of China, causing a browser-freeze here.
And as said, I'm not sure if the hiccup is on the side of Cantr or on my end of the line, just trying to exclude things that aren't the cause.
Already managed to take the pile of Firefox add-ons that I have off the list of suspects thanks to that time it happened on a clean Safari, and since I'm not seeing any other posts about it, I'm thinking it might be something on my side, but I could also just be the first to post about it...

I am having the same issue actually, thought it was the "Greasemonkey" addon I had installed, but it still happens, and noticed that it happens after doing the "show all" option for events in the game.

Glad I saw this post. I started having the same trouble last night and thought it was just my computer acting strange. My browser does not recover from the lockup and I have to kill the firefox process to get it to close.

Hmm, I'm not having this problem, but am using the latest FF on Windows XP. Do you think it could be an OS issue? What are you all running?

Windows 7 home premium 64 bit.


I have had to kill the process a couple times too, but for the most part it does recover on its own after a while.

I'm using XP, Firefox 3.5.5. I've been putting off updating to FF 3.5.7, maybe I'll give it a try to see if it helps any.

I remind you that user can disable JS Cantr contents on its players page.

Just as Cdls has stated, it happens to me when I press the show all button. It does recover after a minute or two but is annoying.

I have Vista and haven't installed the newest of FF but have the one before this new one.. don't ask me for the number thing..

Why you think this is a JavaScript trouble?

I think it is an Ajax problem. Because it freeze when the site is to long (after show all button) And I wanna mark a text. and the 5 secounds actualising comes.

Ajax IS JavaScript. Disabling JavaScript disables Ajax.

For a while, the issue went away.
But yesterday it started happening again.
And not just when the "show all" button is used, though it does indeed appear related to the length of pages.
It does seem to hit me when I have characters who are caught up in some serious events, with much events showing up on a page.

Users can disable the javascript, either on Cantr's own settings or by using something like the FireFox add-on NoScript, but frankly that sounds a bit like Toyota issueing a statement that consumers don't have to use the brakes; I don't know if there are more scripts active on the events page (the page where someone plays their character), but if there are more and prototype.js is the only one out of them that causes this issue, then the better philosophy would be that Toyota fixes that brake so it doesn't end up causing the rest of the car to plow into a building.
The issue seems to be that on the pages where there is much content, prototype.js just decides to go out for a packet of cigarettes and not come back, at least that's the extent of the error message I'm getting after a freeze lasts too long.
In particular, it appears the script breaks and freezes the browser when a page has a lot of content (events) and the page updates.

I'm experiencing the same thing currently. In IE and WinXP and not a lot of memory.