64-bit ArcPy Not releasing Python Process on Completion

2912
17
Jump to solution
06-11-2020 07:02 AM
EricFulcher1
New Contributor III

I'm using a command script to run an arcpy process on ArcMap 10.6 - 64-bit arcpy. On successfully completing the script, the process ends - but doesn't release/kill the python.exe (or pythonw.exe), therefore the bat script hangs and doesn't finish. In the script below, its the arcpy.mapping.ListDataFrames that causes the process to hang (that was fun narrowing down...). Comment it out and python terminates correctly. If i run this in 32 bit python terminates correctly - so just 64 bit. I'm thinking esri bug? Am I missing something?

Thanks,
Eric

Cleaned up script (may have missed something here) but it says the script is Finished.

import arcpy
import string
import gc


def main():
print("Completion Script is Starting")

mxd = arcpy.mapping.MapDocument("D:\WOBufferScripts\LeakSurveyScripts.mxd")
# Running this causes python to not close.
dataFrame = arcpy.mapping.ListDataFrames(mxd)[0]
del dataFrame
del mxd
gc.collect()
print("Completion Script Has Finished")

if __name__ == "__main__":
main()

Tags (1)
0 Kudos
2 Solutions

Accepted Solutions
JoshuaBixby
MVP Esteemed Contributor

64-bit ArcGIS (ArcPy and other software) doesn't support all workspaces that 32-bit ArcGIS does, e.g., personal geodatabases.  If the MXD contains one of these workspaces, a 64-bit process can easily hang trying to process it.

View solution in original post

0 Kudos
PaulBatley
New Contributor III

Hey, We're getting the same issue for both 32 & 64bit and it only started happening around an installed Windows update KB4593226. Prior to the update our python jobs running via Scheduled Tasks runs through but will not run on the next schedule as the process is already running, due to the fact the process never terminates. We have debugged sys.exit() and it is firing correctly. Our only workaround is to have the following code:
os.kill(os.getpid(),9)
This ensures the process terminates and that batch processing continues.

View solution in original post

17 Replies
DanPatterson
MVP Esteemed Contributor

You mention batch file.  Does the script terminate outside of the batch file?


... sort of retired...
0 Kudos
EricFulcher1
New Contributor III

its a runscript.bat file and no it never returns from the python process.

This is just me typing quick but

arcpy script1.py

arcpy.script2.py

It never gets to script2 even tho script1 is in fact finished.

0 Kudos
JoshuaBixby
MVP Esteemed Contributor

How many MXDs have you tried it with?  Does it fail on all of them or just this one?

EricFulcher1
New Contributor III

You have value Joshua! Created new mxd, added 2 layers and the process closed successfully. It was a 10.2.1 mxd originally. wonder what it doesn't like.....

Thank You!

0 Kudos
DanPatterson
MVP Esteemed Contributor

I marked Joshua Bixby‌ 's answer correct since he provided the hint as to the check you didn't try


... sort of retired...
0 Kudos
EricFulcher1
New Contributor III

I don't see how you have the POV to mark this correct. Must get reputation points or something.

0 Kudos
JoshuaBixby
MVP Esteemed Contributor

64-bit ArcGIS (ArcPy and other software) doesn't support all workspaces that 32-bit ArcGIS does, e.g., personal geodatabases.  If the MXD contains one of these workspaces, a 64-bit process can easily hang trying to process it.

0 Kudos
EricFulcher1
New Contributor III

Thanks Joshua. Actually - the mxd has about 20 SDE Feature classes. I found if I rebuild the mxd from scratch (same FCs) - same issue. But by trial and error - if I remove one FC (Oracle SDE GDB) it magically works now. Go figure.....Doubt I'll get esri to debug this. Other FCs in the same feature dataset dont' impact it. weird......

0 Kudos
ChrisWalsh
New Contributor

Is there a way to identify incompatible workspaces? I'm currently running into this similar issue where an automated publishing script running on 64 Bit Arcpy doesn't release it's process. This script has been working for years for multiple mxd's, but has only just now shown this behaviour after we upgraded to ArcServer 10.8. 

0 Kudos