The last bit: ...(the one created by the Widget Converter) onto the Widget Converter, and click the button. This will create a new widget called KonStat 2.widget. You may wish to delete the old one and rename this new one to KonStat.widget, or just run this new one instead.

Cheers!

Hmm... there was a limit to how long a post can be. Ok, here's the rest:
From this:
**** original code ****
<action trigger="onLoad">
<!--
var SPACER = 4, RIGHTSPACE = 2;
var url = new URL();
check();

function check()
{
url.location = preferences.urlToUse.value;
changeTimer.interval = preferences.checkInterval.value;
status.tooltip = "Click here to go to: " + url.location;
**** original code ****

To this:
***…* updated code ****
<action trigger="onLoad">
<!--
var SPACER = 4, RIGHTSPACE = 2;
check();

function check()
{
var url = new URL();
url.location = preferences.urlToUse.value;
changeTimer.interval = preferences.checkInterval.value;
status.tooltip = "Click here to go to: " + url.location;
**** updated code ****

4. Save the file and drag-and-drop the whole folder (the one created by More

I fixed the memory leak on my local version. I'm no Jaca Script programmer, but I fooled around a bit with the code and found that the URL object seems to cache the web page each time it fetches it. So we need to clear this object each time. I don't know if there is a Clear method on this object, but an easy way to clear it is to New it each time. Here's how you do it:

1. Dounload and run the Widget Converter widget.
2. Drag-and-drop the KonStat.widget file from your widget folder o…nto the Widget Converter, and click the button. This will create a subfolder called KonStat.
3. Open the KonStat.kon file in Notepad or your favorite plaintext editor and do the following cange:

From this:
**** original code ****
<action trigger="onLoad">
<!--
var SPACER = 4, RIGHTSPACE = 2;
var url = new URL();
check();

function check()
{
url.location = preferences.urlToUse.value;
changeTimer.interval = preference More

Tu be perfect, A sound option (Wav/Mp3) if a url go down would be the only thing missing to me =)

I experience the same problem as boxfan, the widget is leaking memory. About 3K a second. After about 14 hours it was using 113MB. This is a shame, because I'd really love to keep this widget running. It is a great idea, and it is very useful for me to check if my web service is up and running. I have had some problems with the server it is running on lately, but sometimes it can go hours before I detect if the server has locked up and the web service is not responding to my clients anymore.… So please fix this memory leak, so I can use this potentially excellent widget. I can't use it as it is now, because I need all the memory for other applications. I will give you a higher rating as soon as this is fixed. Good luck! :-) More