Hello,

Hmm We've never encountered this before.

Does it do it if the client did not have a DB file open?
When you go into Task Manager how much CPU and memory is Sesame client using?
Is Sesame installed on each machine or using a mapped network drive or UNC path and running it off the server?
How are you closing Sesame? (File->Exit, Red X or custom button)

-Ray

Hi Joe,

There is a bug in 2.5.3(fixed in 2.6.0) where under certain circumstances sometimes a client process would start, increase client count, but the client window would never display. This sounds almost like the symptoms you are seeing except it would never lock up the client computer, just merely hold up a license on the server.

X'ing out is fine, Was just wondering if there was a custom button that might be doing something. The only issues Save should cause is people seeing Sesame pause as the Server does a full save of the database, although it can cause people to become click happy as the client pauses.

-Ray

Nighthawk, what has changed on these systems? I've looked through your previous postings and clearly, you were not having this issue until recently.

Does this happen on all of your client computers or just some of them?

On the computers where it does happen, does it always happen?

You stated that it happens even when no database is loaded, does it also happen if the Sesame is run "standalone" rather than client/server? How about standalone with no application loaded?

Does it ever happen if you are running one of the sample applications, like Customers.db, etc?

You say that the OS is locked up when this happens, yet sometimes (not every time?) you are able to hit CTRL-ALT-DEL and bring up the task manager. When locked-up, is the mouse able to move at all. If so, does the start menu appear if you click on it? Can you move or resize any windows or double-click on any icons?

When this happens, is the Sesame window still on the screen? Does it update? Is it blank?

Ray asked about memory and CPU usage and you reported that both were at zero. A process may be using zero CPU, but isn't actually loaded if it is using zero memory. If that is the case, then for reasons unknown, Windows is holding on to an entry for Sesame, even though Sesame has ceased to be loaded, or Windows is misreporting the amount of memory that Sesame is using, which must be at least - some.

I'm not asking if you run Sesame in standalone mode or with sample databases, I am asking you to run Sesame in standalone mode and/or with sample databases and tell me if the problem ever happens - as a diagnostic.

What I am trying to determine is whether the problem is coming from your application (so I need to know if it happens with other applications), is coming from the network (so I need to know if it happens standalone - which doesn't use the network), is because the Sesame executable was corrupted when copied, downloaded, or executed from a remote drive, is due to interference from a virus, security program, or firewall, or if your OS is badly corrupted or misconfigured.

If it was merely a bad Windows update, we would be getting complaints from everybody that received the update, hundreds, if not thousands, of people. But at this point, you are alone in reporting this issue.

If I remember correctly, you have a relatively large application that has been growing rapidly. Is it possible that this is occurring because your users are kicking off a lengthy operation and then hitting the "X" to close Sesame while the server is still trying to complete the lengthy operation and the client is waiting for that completion? Does this ever happen while there is little to no CPU activity on the server?

NightHawk wrote on Jan 20^th, 2016 at 9:50pm:



What are the size of the DB and DAT files? 200k records isn't all that much. If I had to guess, It sounds like at about that size the Sesame Server process wants more RAM then the server computer has available so the server system starts swapping and using the hard drive for additional RAM which is SLOW..

-Ray