This is with Mantis B19 on Windows XP professional SP 1.

After installing the JRE, when I restarted my laptop, jucheck.exe went into
some kind of infinite loop. This made my laptop behave very badly. The
problem persisted across several rebdots.

We need to figure out what is going on here and fix it before FCS.
Having anything like this happen with any frequency to end customers
would be a very serious problem.

The problem was very reproducible at home but I can't reproduce it
in my office. (This is why we are doing at-home testing, right?)

At home I used Visual Studio to get a backtrace of jucheck.exe :

  ntdll.dll!77f7670b()
  user32.dll!77d69f56()
  user32.dll!77d4d07a()
  jucheck.exe!ATL::AtlWaitWithMessageLoop() Line 5451 + 0x17 C++
  jucheck.exe!CDownloadTracker::CreateSystemTrayWindow() Line 495 C++
  kernel32.dll!77e7d33b()

Unfortunately this doesn't really tell us very much (sorry).

Additional configuraytion data which may or may not be relevant:
My home environment uses an 802.11b wireless network. I had my
laptop configured for work, which meant the proxy configuration
was trying to use an inside-the-firewall proxy server, even though
the laptop was now outside the firewall.

###@###.### 2003-03-30

----------------------------------------------------------------------------

I just reproduced the problem again. My laptop was on the open internet
but my proxy settings were configured to use a Sun internal proxy server.

When I started up, jucheck.exe was busy eating over 80% of the CPU.

I went into the internet control panel and turned off proxies.

Jucheck.exe immediately dropped to 0% CPU use.

So I think this confirms that the problem I'm seeing is around what
happens if you have a bad proxy configuration.

###@###.### 2003-03-31