Skip to content
← Acrobat for Windows and Mac

Feature request / Bug report

Acrobat for Windows and Mac: Other

Categories

JUMP TO ANOTHER FORUM

(thinking…)

LogTransport Application (LogTransport2.exe) maxes out CPU usage

As the title says, LogTransport Application (a process listed under Adobe Acrobat DC in the Windows Task Manager) basically runs at full throttle and maxes my CPU (well, one core).

I can tell when this starts because my laptop's fans start going.

This problem started around about the most recent Acrobat update, so mid May.
Current version is:
Acrobat DC, 2020.009.20065
Windows 10 Pro 1903

1 vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Michael Tobin shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Michael Tobin commented  ·   ·  Report

    I installed the update, and so far everything looks good; I haven't seen the LogTransport application taking up all of my CPU since.
    Thanks!

  • AdminSumita (Software Engineer, Adobe) commented  ·   ·  Report

    Hi,

    We have released an update that fixes the issue reported in this post. Please update your installation of Acrobat DC to the latest version 20.009.20067 through help > check for updates to get the latest patch. Thanks for all your feedback.

    Thanks,
    Sumita

  • Michael Tobin commented  ·   ·  Report

    Hi Vinod,
    A fix would be appreciated. If you need any more information please let me know.
    Several of my coworkers are experiencing the same problem: laptop fans start running at full speed, and LogTransport Application is consuming all the CPU of one core of processor.

  • AdminVinod Dobhal (Software Engineer, Adobe) commented  ·   ·  Report

    Hi,

    We are extremely sorry for the inconvenience caused due to the issue. We are not able to reproduce the issue in-house but, have found a potential fix for the problem. We will be releasing out a patch very soon that should fix the issue.

    Thanks,
    Vinod