Revision history  [back]

We might be able to diagnose this from the error log, which is the file ide.log in the User Settings directory listed in Wing's About box. You can submit that to us with a bug report from Wing's Help menu, or just email us all or the relevant part (based on the time stamps). It would also be useful to know if you have the debugger active during the freeze and whether you're using AI, as those might be more likely to cause this.

Another thing you could try if this is at all predictable is to collect a profile across a freeze:

• Use Edit -> Command By Name and enter: internal-profile-start
• Let it freeze and unfreeze
• Use Edit -> Command By Name and enter: internal-profile-stop
• Then submit a bug report from Wing's help menu and check the box to include the error log

That might even work if you can't predict the freezes, if the CPU used during the freeze is large enough to overshadow what's used in the interim so that the relevant calls show up in the profile.

You can also bind a key or toolbar icon to those command names (use internal-profile-start,internal-profile-stop as the command name, one word with comma separation, to set up a toggle) in case that makes it easier to start/stop profiling.

Thanks very much for reporting this!