Running Security - stalling processing?

[MWearne]

I've been working on some new benchmarking and I'm getting inconsistent results and it seems to be due to this 'Running Security' event. Is anyone else seeing this in the bottom left corner for extended periods of time (minutes) when calculating toolpaths? I am on an internet license and it does look like code meter and mastercam are more active on the network than usual during this time. Surely it isn't phoning home every time I calculate a toolpath, right?

-these are large toolpaths, several are 100,00k+, it wouldn't be sending this data would it? (I do not click the send feedback when installing)

-sometimes the 'Running Security' is only on screen for a second, at most. I can't find a pattern for when its one second and when its 3 minutes.

[gcode]

Maybe it's phoning home to check if a specific type of toolpath is authorized on the license 

Could you borrow a license and run it locally to see if processing times improve? 

[MWearne]

I've narrowed it down to a Surface Finish Contour op. Normally it takes 7-8 seconds to regen. If the Running Security is triggered, it takes 3:30ish.

Running Security seems to only get triggered when first opening the file, but not every time.

I disabled all internet connections, was able to get the Running Security to trigger, still 3:30ish regen time.

So...I have no idea what's going on. Guess I'll have to send this one in.

[billb]

Yes, please send it in. We may be able to provide insight. When it regenerates quickly, I suspect that it is able to reuse cached data. When opening the file the first time, maybe there is no data cached (or it is not reused). 

[harleysport]

I have had it run for an hour or more...yes, surface finish contour.

[billb]

If you have a slow finish/contour toolpath, please send it in and we will have a look. 
 

We recently discovered a regression with bull nose tools (now repaired). 

Edited July 3, 2023 by billb