Hard disk activity after cropping image

  • 1
  • Problem
  • Updated 6 months ago
For years (going back at least to Snagit 13), I've noticed that after cropping an image, when I then close the Snagit Editor, there is about 2-3 seconds of heavy activity to the hard disk which even slightly delays the closing of the Editor window.

I saw in the most recent Snagit changelog, for version 2020.1.0, an entry that says this:

"Improved Editor performance when cropping images or working with cropped images"

I thought maybe that has fixed it. But it seems to have made no difference at all. When closing the Snagit Editor after having cropped an image, I still get a couple of seconds of intense disk activity. Is this issue known about? Also, what did the above entry in the changelog refer to if it wasn't this?
Photo of Neville


  • 74 Posts
  • 21 Reply Likes

Posted 6 months ago

  • 1
Photo of Joe Morgan

Joe Morgan

  • 9083 Posts
  • 4787 Reply Likes
Have you tried resolving this through Tech Support?

If I crop an image and save the changes.
Then close the editor.
It closes immediately, no delays, it closes in a fraction of a second.

Monitoring my disk drives, there is virtually no activity an any of them.

Photo of David Howell

David Howell, Employee

  • 129 Posts
  • 49 Reply Likes
The performance improvements that changelog entry is referring to is related to the actual cropping operation (when you're dragging the handles to resize). If you are seeing a delay when closing the editor, from what I understand, those changes were not related to that.

Snagit does all kinds of I/O on program exit (saving unsaved capture edits, saving configuration files, etc.) I am supposing that you do not see this intense disk activity if you do not crop any of your images. But I cannot think of why that would be the case. If anything, if you crop a large image to be smaller, it should save faster. If you have the "Delete cropped content" OFF in preferences, it still saves the entire image, so it wouldn't be faster in that case, but it should at  least be as fast as if you didn't crop.

There might be some clues to the disk activity (speed of) if you look at the Windows Task Manager (go to the Performance tab). Our tech support can help with this too.