topic Re: Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ? in ArcGIS Pro Questions

Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ?

JoabelBarbieri — Fri, 24 May 2024 19:36:12 GMT

Anything you try to cancel in ArcGIS PRO just gets hanging and spinning and it won't finish. It seems PRO tries to finish the process before cancelling which is a HUGE waste of time and resources. Having to kill the exe, losing all your work is a constant. ESRI must address this issue

Example where I canceled and it's spinning for MORE than 15 MINUTES !!!

Re: Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ?

TheodoreF — Thu, 01 Aug 2019 09:45:24 GMT

Yes! This is so annoying. To cancel a process I have to open task manager and kill ArcGISPro.exe! So annoying.

Even something like selecting a subset of points from a layer to export to a new feature class, then cancelling that as I realise I already have what I need. The cancelling message hangs indefinitely. I can't even cancel the cancel.

Re: Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ?

DevinRoth — Thu, 09 Apr 2020 17:00:28 GMT

Does anyone have anymore information about this?

Is there a way to force cancel a geoprocessing command that is not responding short of restarting the program?

Re: Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ?

DevinRoth — Fri, 24 Jul 2020 15:33:07 GMT

Following up on this to ask if this behavior has been improved in the latest version.

Re: Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ?

SBrandenburg — Mon, 19 Oct 2020 21:37:29 GMT

Same thing still happening in Pro 2.6.2.

Re: Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ?

Anonymous User — Fri, 08 Jan 2021 15:29:23 GMT

Any updates? Similar to those above, I have to kill the programme through the .exe. Surely this is not how the programme was designed? I am using 2.6.1 - Is there not an answer to this?

Re: Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ?

NickCook — Fri, 05 Feb 2021 21:07:30 GMT

A month later.... same issue. I hit the cancel button and it just says Canceling... above it in my history, the red stop button turns grey, and then it freezes and doesn't cancel anything. In the meantime I can't use the file involved with the cancelled geoprocessing because its hung up on the cancel. So I have to restart ArcPro. Why is so much basic functionality that worked fine in ArcMap (32-bit) now SO much slower and buggy in 64-bit? It has Microsoft's fingerprints all over it...

Re: Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ?

MichaelLedwith — Mon, 01 Mar 2021 15:11:20 GMT

It's still the same in 2.7.1.

I cancelled a SelectByAttribute query (~900,000 objects) last Friday and the cancellation still wasn't finished on Monday morning. The Kill command in ProcessExplorer is the GIS-expert's best friend.

Re: Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ?

YvonneFederowicz — Thu, 10 Jun 2021 01:40:16 GMT

Still the same! 14GB later... I killed it, thanks for this thread -- I kept hoping it would end gracefully...

Re: Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ?

MichaelTomiak_WSP — Thu, 04 Nov 2021 13:19:26 GMT

Still occuring - any issues why? How do we alert to ESRI?
I've jsut had to kill by .exe and lost the work I had done ....

Re: Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ?

KoryKramer — Thu, 04 Nov 2021 13:20:40 GMT

Are you working with a geoprocessing tool or the Explore tool to identify a feature (open its pop-up)?

I'd recommend first working through as there could be a number of issues at play (data location?) and as those steps indicate, if you've exhausted suggestions there you can contact technical support to investigate further.

Thank you

Re: Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ?

MichaelLedwith — Thu, 04 Nov 2021 19:17:45 GMT

Thanks for a response... any response - even if it's a few years too late.

But seriously, the fact of the matter is that AG Pro attempts to complete some part of the task at hand - a sub-process perhaps. If you're working with a large dataset, AG Pro hangs. This is something I've experienced plenty of time during the past ten years or so. And when I say "plenty" I mean dozens.

As for contacting "technical support", good luck with that. We're usually the ones that explain the solutions to ESRI support... 🙂

Re: Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ?

MichaelTomiak — Wed, 23 Feb 2022 16:45:49 GMT

02/2022, a pandemic has come and gone and no resolution XD.
Any resolutions to this? @esri_uk

For context this time, I started a process of Raster Mosaic (all data is local), after starting I realised I had what I needed else where, so tried cancelling, to find it the blue circle which went on for an hour. So I just killed the .exe.

Re: Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ?

KoryKramer — Wed, 23 Feb 2022 17:02:28 GMT

@MichaelTomiak you mention "Raster Mosaic". Are you using the Mosaic tool, Mosaic to New Raster tool, or something else?

I just tried with Mosaic and was able to cancel the process:

And Mosaic to New Raster:

If you have reproducible steps that demonstrate the cancel functionality on a geoprocessing tool to not work, let us know and we can take a look. Or you could report the bug here https://support.esri.com/en/report-bug (imperative to have steps that reproduce and demonstrate the problem).

Thank you.

Re: Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ?

MichaelLedwith — Thu, 24 Feb 2022 08:33:45 GMT

We naturally appreciate all "attempts" to help... I'll leave that thought there.

Seriously though, this problem has ABSOLUTELY NOTHING to do with the specific tool being used. It happens all the time irrespective of the tool or model. It might - might - have something to do with the size of the data set being processed but it just as easily could have something to do with AG Pro's incessant need to map up inordnat amounts of RAM and then not use it or release it.

Re: Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ?

skyhook — Fri, 15 Apr 2022 19:16:55 GMT

I'd like to echo what's been said. This is a chronic problem. Incredibly frustrating.... It's only like 20% of the time when I try to cancel any geoprocessing tool. This bug doesn't seem to discriminate. Big dataset, small dataset, ArcPro version, data format, etc.... Currently, "cancel" has been frozen for better part of an hour for "calculate geometry attributes" on a dozen simple polygons......

Re: Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ?

MeganBleess — Fri, 29 Apr 2022 23:46:45 GMT

For what it's worth, I started at 11:45am using the import XML Workspace schema geoprocessing. I let it run, had lunch, had a meeting and around 2:20pm I clicked cancel as it seemed hung up at 3%. It's been canceling ever since. It is now 5:45pm. The XML schema is for a feature dataset with 3 feature classes. NO DATA. I'm going to kill Pro via Task Manager and pick up again Monday. What a waste. I could have drawn the files faster with crayola.

Re: Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ?

DorianneDysart — Mon, 09 May 2022 15:00:20 GMT

Same thing in ArcGIS Pro 2.8.3, going to make go make some coffee and maybe a walk around the building while its hanging lol

Re: Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ?

JoabelBarbieri — Fri, 02 Sep 2022 14:05:28 GMT

We ARE at version 3.0 and the speed to cancel anything seems to be getting worse.

Waiting on a split to cancel for about 20 minutes now!!!! This can't be normal ESRI. Please do something!

Re: Why is ArcGIS PRO so slow to cancel a simple geoprocessing tool ?

jyh — Mon, 03 Apr 2023 13:00:56 GMT

Just to update this thread - cancelling geoprocessing in Pro is still a problem in April 2023. It happens every time, no matter what tool it is, whether from a standard toolbox or ModelBuilder, or the size of the dataset. And Pro hangs so I can't do anything else while it's cancelling, so I often wind up using Task Manager to shut it down. Sometimes, after a cancel actually finishes, I find that it produced output anyway. Using Pro 3.03 now, but this has been the case with every version I've used going back to 2.1.