Performance with API 1.1

[AndyKaufmann]

I just upgraded the 1.0 FGDB API code with the 1.1 code and am now seeing such a severe lag when I call CloseGeodatabase (even with a very small GDB) that I can't even test my code in debug mode.  The release build (FileGDBAPI.dll) shows a lag too, though not nearly as severe.  Is this something I have to live with?

[LanceShipman]

64-bit Win7. Local drive for development. I'm not sure how I should "clean" my machine.  I'm not quite ready to wipe the hard drive and reinstall everything. 🙂  Do the pdb files that come with the dlls mean I can stop inside CloseGeodatabase and see where it's stuck?  I haven't been able to so far by telling VS the location of the symbol files.  Currently when I break in the debugger it stops in thread-related code (lock) or in the function CatalogRegistry::CatalogRef::Release() under CatalogRegistry::Unregister() .  That much in can see in the call stack.

A clean install in my case means a machine that does not currently have the API on it. The pdb files will not let you stop in CloseGeodatabase. I've rebuilt the samples both debug and release, 32bit and 64bit and not seen the slowdown.

[AndyKaufmann]

BTW, I have the same problem with 1.1 for Visual Studio 2010.  Locks up when I hit CloseGeoDatabase.
😞