Quote:
Originally Posted by chaley
Thank you for taking the time to continue tracing this.
|
No need to thank you, it has been a way to entertain myself as I have to stay at home with a cold
Quote:
Originally Posted by chaley
What those traces say is that python garbage collection is collecting (deleting) the current database, thus closing it or a copy of it.
In other words, I think that something is opening the database of the current library or creating a copy (copy.deepcopy()) of an open instance variable, saving it as a local variable. When GC (garbage collection) is called that local copy is closed. There are timing problems here. The local variable might not be collected in some situations.
The only way I can see to verify this is to remove the plugins one at a time to see if the problem goes away. I would start with Action Chains, as I checked SaveCompositeColumns and it doesn't reopen or make a copy of the DB. If the plugin is found then we can look for why the variable that GC collects is created.
I hope Kovid notices this thread. He will probably have ideas on why it is happening and how to find it.
|
I've already removed a lot, including what you mention, and same issue. I think I'll follow Kovid's suggestion for checking this.