Not Responding

[bniemerg]

I'm running Zeus 3.97s on Windows 7 64bit and randomly but at least once a day Zeus will lock up and Windows will report it as not responding and force quit.

This has been happening for quite some time, and with previous Zeus versions but not as frequently as it is happening now.

Any help is greatly appreciated.

Thank you.

[jussij]

I'm running Zeus 3.97s on Windows 7 64bit and randomly but at least once a day Zeus will lock up and Windows will report it as not responding and force quit.

There are at least two things found in Zeus that are run in the background.

The first is the tag rebuild of the current workspace and the second is a check of the file status, which happens every 3/4 of a second.

If any of these tasks take a long time then you will see the 'not responding' status from Windows.

In normal operation I do not see this, but I have seen it happen on a machine running several background builds and thus having that build consume most of the free CPU cycles.

I have also seen this when a massive workspace was loaded into Zeus and it was doing a tags update.

I have also seen this for a network file (i.e. \\some server\some folder\network file.txt) and Zeus was having trouble connecting to the network to get the file status.

Naturally for this case, while Zeus is showing the symptoms, the real problem is the slow network.

If you have a large workspace loaded, try using the Tags, Rebuild menu which will rebuild the tags database (which might be corrupt).

it as not responding and force quit.

In all the above cases, you should not have to force a quit, but instead just wait as Zeus should eventually return.

The first time I ran into the file network issue I though Zeus had crashed, but after waiting one minute (i.e. the timeout period for the network) Zeus came back to life.

But if you are seeing the network problem, make sure you close the network file otherwise the same thing is bound to happen.

Cheers Jussi

[bniemerg]

I do have some fairly large projects in my workspace however none of my projects use the "Enable the built-in workspace ctags builder" option. Would the tag rebuild still activate? Is there a way to disable it?

The not responding problem just occurred this morning and all of the files I currently was editing were on my local hard drive, which is usually the case. I do have some network files in my projects but I'm guessing Zeus only scans the open files correct?

I didn't wait to see if Zeus would return this last time but if it happens again I will try to be patient and wait it out.

Thanks

[jussij]

Would the tag rebuild still activate?

No.

Is there a way to disable it?

I think you have

You can confirm this by checking the times stamps of the tag database files found here:

Code: Select all

C:\Users\<current user>\AppData\Roaming\Xidicone\Zeus\zTags

Also if it is the tags build you should see a message in the status bar.

I'm guessing Zeus only scans the open files correct?

That is correct.

Cheers Jussi

[tmas]

I can always see it pauses at the same file path everytime I open the workspace saying "Updating tags for project: <project> <path >"

And at the same time, the cpu loading is maximum.

I don't mind sending you a 40MB workspace file - as I just start trying the beta version and there ain't any secret just open source projects...

[jussij]

I can always see it pauses at the same file path everytime I open the workspace saying "Updating tags for project: <project> <path >"

Whenever a workspace is opened Zeus will go through each of the files in the workspace to see if they have changed.

This is what that update message is referring to.

I can always see it pauses at the same file path everytime I open the workspace saying "Updating tags for project: <project> <path >"

Is the file that shows the pause a big binary file

If it is just remove that file from the workspace as it can't be tagged.

Note: Removing the file will not touch the file on the disk.

I don't mind sending you a 40MB workspace file

And this is the answer to the long pause

That is a massive workspace, which obviously also means you have a massive number of files in the workspace and hence the long delay updating all the files in that workspace.

What I would suggest is doing the following:

(1) Open the workspace
(2) Use the Workspace, Options menu
(3) In the Tags panel select the Disable the automatic updating of the tags file option

With these settings, the tags update will not happen whenever the workspace is opened and as such it should open very quickly.

But, naturally that also means you will have to occasionally do a manual tags update.

You can do that manual update using the Tags, Make menu.

Cheers Jussi

[jussij]

Just recently I noticed something similar whereby Zeus would report not responding for a few second after a file was saved.

At the time for Zeus had a large C# ASP.Net workspace open and Zeus was doing a tags update for that workspace.

I had a look at that process in Task Manager and noticed that it was using over a gig of RAM

After are used the Tags, Rebuild menu the RAM reduced back to a more normal 80,000 kBytes.

So I suspect there must be some sort of bug with the tags database code, as it is constantly growing the database.

The tags rebuild fixes this because it throws away the current database and then recreates a new one.

Cheers Jussi.