Hi Ian,

    what platform are you on?  If you're on Mac OS X you can send SIGUSR1 to the process and a stack trace will be written to stdout that will be visible on the system console.  Of course if you started the system on the command line you'll see the output there.  You can identify the process via

$ ps axww | grep -I squeak

On linux I don't know if the output of a desktop launched app goes anywhere but would expect it to be much like the Mac; there will be a visible output stream somewhere.

On Windows I have no idea but I assume you're not on Windows cuz we don't have the 64-bit JIT VM working there yet.

_,,,^..^,,,_ (phone)

> On Apr 28, 2017, at 2:11 AM, Ian Trudel <ian.trudel at gmail.com> wrote:
> 
> Hi,
> 
> I saved Squeak image yesterday and open it today, Squeak displays everything as I left them off but is unresponsive and taking roughly 17 to 18% of the CPU. Running on Squeak5.1-16549-64bit-201608180858-Windows. 
> 
> What should I do?
> 
> Ian
>