SnagIt Memory usage

  • 1
  • Problem
  • Updated 5 months ago
Recently I noticed my computer has slowed WAY down when using SnagIt. Since the program opens when I start my computer I thought it was just the machine warming up and opening all of the background programs. When I look at the Windows Task Manager I can see that SnagIt is using 1,500,000 to 1,600,000 K of memory when it runs! That is about 100,000 - 200,000 more than Adobe Photoshop uses. There has got to be something that can be done to keep the tool from using so much memory and cache when it is in the background or in use. Does anyone know what is causing this or does the tool really demand this much space to work?
Photo of caleb.castro

caleb.castro

  • 7 Posts
  • 0 Reply Likes
  • frustrated

Posted 5 months ago

  • 1
Photo of JL1

JL1

  • 209 Posts
  • 95 Reply Likes
On my Win 7 Pro 64-bit machine, SnagIt 18 uses 237,400 K. I've never seen memory usage approaching yours.
Photo of Paul

Paul

  • 1200 Posts
  • 933 Reply Likes
Won 10 Pro SnagIt 2018  Capture 58.5 MB, Editor 49.8MB when idle in background.

Caleb - if this persists you might want to open a support ticket
Photo of Joe Morgan

Joe Morgan

  • 5822 Posts
  • 3042 Reply Likes
Tech Support is currently working on a memory leak  for SnagIt 2018.

See this link.
https://feedback.techsmith.com/techsmith/topics/memory-overflow-in-snagit-2018-build-18-2-0

Regards,Joe
Photo of brad

brad

  • 1 Post
  • 1 Reply Like
When I run Snagit one-step, open up Windows Task Manager by doing absolutely nothing I sit here and watch Snagit32.exe Memory continue to grow. I'll eventually get a windows notice popup that it's using too much memory asking me to close it. By this point the memory usage is over 6,500,000. This just started after last upgrade. I'm running Win 7 Pro, 64-bit.
Photo of caleb.castro

caleb.castro

  • 7 Posts
  • 0 Reply Likes
Killer feedback everyone! Thanks for chiming in so quickly. @Joe I will follow that thread to see what updates come from the team and @Paul I am going to open a support ticket to cover all my bases. Once I find a solution I will share it for everyone here in the event it might help someone else.
Photo of Dubie

Dubie

  • 998 Posts
  • 776 Reply Likes
Photo of caleb.castro

caleb.castro

  • 7 Posts
  • 0 Reply Likes
Hi everyone,

The support team reach out right away and they have released a new update this morning. 18.2.1

http://www.techsmith.com/download/licenses/snagit.asp?ver=18



Once I made the update, everything began to work as designed. All set here! I appreciate everyone's help.

Photo of kevin

kevin

  • 1 Post
  • 0 Reply Likes
I am seeing this also.  SNAGIT32 is hogging tremendous  ammounts of memory and does not release it.  I am running Windows 7 64 bit.  Over a weekend SNAGIT will slowly grab all the memory until system becomes unstable.  I have to shut the SNAGIT app down and it releases the memory.  It never did this before...I've used it for years....might have something to do with the new 2018 version.
Photo of Peter Bagge

Peter Bagge

  • 2 Posts
  • 0 Reply Likes
Hi Nate,I am currently using the latest version of SnagIt (2018, 2.1), but I am still encountering the same memory leak problem on my Win 7 Laptop.It seems that the bug fix has been left out in the version? Can you check this out. Our tech support is getting frustrated after installing the software already twice fo me.Glad for some help!

Best Regards,Peter BaggeProduction Development Manager
Otava Publishing LtdFinland
Photo of Joe Morgan

Joe Morgan

  • 5767 Posts
  • 3010 Reply Likes
You should be reaching out to tech support directly. This is a user to user forum.

TechSmith jumps in from time to time. However, for the quickest response to an issue.

This is a Free Service............... Submit a ticket


       https://support.techsmith.com/hc/en-us/requests/new

Or call, >>>

 Toll Free: 800.517.3001 (U.S. & Canada Only)

8:00 AM to 7:00 PM EST Monday through Friday

Regards, Joe

Photo of Peter Bagge

Peter Bagge

  • 2 Posts
  • 0 Reply Likes
Allright.Sorry for the wron address!
Thanks Joe. Br, Peter