# 2579 Dropping a Table Opened by a Server-Side Procedure Can Cause Server AV

---

After upgrading to DBISAM 4.26 I started having a crash when running in client/server mode. The crash has recently reappeared and I have since determined that this was because I had re-enabled FastMM's FullDebugMode and friends.
Probably this was the problem all along, rather than having to do with the specific version of FastMM.

The other possibility is that something is reusing freed objects or otherwise misusing memory. According to this theory FastMM4's FullDebugMode's practice of clearing the contents of destroyed objects is revealing the bug.

My sample project works as follows:

Server project: starts a server and makes a server procedure available. When called, the server procedure opens a TDBISAMTable connected to a memory table and then destroys it.

Client project: connects to the server, creates a memory table, calls the server procedure, and drops the memory table. When I close the client application (and thus disconnect from the server) I get a crash on the server.