Indigo 6.0.1 in an infinite loop

Hello: My Indigo 6.0.1 ends up in an infinite loop consuming 100% of the CPU. I'm not sure what's triggering it - but my only way out of it is to Force Quit indigo and restart the machine.

I'm running it on a 4GB 2009 Mac Mini. The machine works fine in every other way.

What can I do to provide information on its behaviour that might help debug the situation?

Please let me know and I'll do all I can to help.

Thanks,


Wayne

[matt (support)]

Hi Wayne,

What plugins are you using? Try temporarily disabling all of them by renaming this folder:

/Library/Application Support/Perceptive Automation/Indigo 6/Plugins

to:

/Library/Application Support/Perceptive Automation/Indigo 6/Plugins-temp-hidden

and then restart the Mac. Does the client still hang then?

And does Indigo's Event Log files have any clues?

Hi Matt: Thanks for the reply. I am using the Cynical plugin - and there have been some challenges - but I can't be specific. What I'll do is let the problem happen again - because it seems to happen within 48 hours and then check the log and send it to you.

If I can suggest, you might want to put some troubleshooting facility in your Help menu that pulls the log and emails it to you.

We do this in the analytical systems we develop. It makes figuring things out a whole lot simpler.

That said - you are easily among the best s/w developers I've ever encountered. First class all the way.

I'll get back to you with the log. Should I post it here?

Thanks, Matt

Wayne


PS - I just found the logs - i'm not sure there's anything there. But i've attached it here

[jay (support)]

If I can suggest, you might want to put some troubleshooting facility in your Help menu that pulls the log and emails it to you.

Select the Help->Email Log... menu item - the default email is the right one.

[jay (support)]

When it happens again, open the Activity Monitor application and see which process is actually sucking up the CPU. If it's an "IndigoPluginHost" process (there are likely multiple), select it and click the "Inspect" button. In the resulting window, switch to the "Open Files and Ports" tab and one of the lines should show you the plugin's name (look for ".indigoPlugin" in the line).

Thanks for the tip on emailing the log - good work!! I missed it!

And I just sent the log along - i'm in that situation again.

Both IndigoServer and IndigoPluginHost are consuming about 50% CPU each.

I've only got one plugin - the Cynical one - and it looks like it's the culprit (likely, i'm the culprit, I probably have something set up wrong).

if you have any comments or further insight, please let me know.

Thanks for your help.

Wayne

[jay (support)]

Use the Activity Monitor to kill the IndigoPluginHost process and see what happens.

Also, a tip: you might want to put a bit more information (like your forum name) into the subject line of any logs emailed to us - so we can make the connection. We did this time, but sometimes if we're swamped we may not...

Right! Thanks for the tip on the subject line - connect the dots.

I did as you suggested previously - I moved the plugin to a temp-hidden folder and restarted.

So the plugin is not operating currently.

I may be incorrect - but I know it was set up in Indigo 5. What I'm unsure about is if I messed with it at all after installing 6. Perhaps, then,there is an issue with the cynical plugin and Indigo 6.

If I can help test, please let me know.

Thanks for being there.

[jay (support)]

So, did killing the IndigoPluginHost process free up the server?

HI Jay: Yes indeed, killing the plugin stopped the cycling dead in its tracks.

Is there any testing I can do?

There must be some settings that I have in place that are causing this to happen. Then again, I suppose, between the plugin and Indigo, one or the other or both together ought to prevent this from happening.

Again, please let me know if there's anything I can do to help.

[jay (support)]

There's another thread discussing this issue that you can monitor (assuming it's the same plugin). The developer knows about the issue.