PDApp.log file is a monster - can I control it?

I was experiencing the same problem. Reinstalling Lightroom seems to have resolved it.

Having a similar problem here. For me Lightroom CC is the culprit.  While LR is running (even if it is idle), PDApp.log grows constantly, chewing up HDD space at an alarming rate!  PDApp.log remains after LR is closed, and needs to be deleted manually.  I never recall this happening with any prior version of LR, which I have been using since LR 1 beta!  Resource monitor shows disk write of 12MB/s to pdapp.log while LR runs and then tapers to zero after LR is closed.  This is crazy!  I can't use LR because it gobbles up hard drive space until the drive is fully consumed, which doesn't take very long at 12MB/s. Adobe please help!!

Adobe people - care to chime in here?

Was/Is there a fix?

This issue is very problematic!!!!

So my log files are in ~/Library/Logs (guessing they got shifted recently) - mine went ballistic last night when AAM went into a very silly place and decided to spent the entire night writing log entries..

I killed the AAM process (using Applications/Utilities/Activity Monitor - which is where you could see it going awol and chewing up CPU and disk) - but for those of you comfortable with Terminal ps and good old kill will do just fine

Then I ran grand perspective to find why the disk was suddenly full - the result you see in the previous post, just deleted the excess logs and rebooted the machine - all fine again.

At this point I decided to do some reading and found the following:

You can do some things to control the logs with ~/Library/Application Support/Adobe/AAMUpdater/1.0/AdobeUpdaterPrefs.dat

If you want to disable the auto updates - take a look here (this is a widely published link to solve this problem if you spend some time googling) and works fine: Disable auto-updates | Application Manager | IT administrators

However, I'm *trying* a slightly different approach

I've just...

Edited: ~/Library/Application\ Support/Adobe/AAMUpdater/1.0/AdobeUpdaterPrefs.dat (it's an xml file - so any friendly text editor will work - vi is your pal)

Look for: <LogLevel>2</LogLevel> (around line 4)

I'm not 100% sure which way the number goes or indeed if the logging level parameter applies to all logs - but I'm guessing that making the number lower will reduce the verbosity somewhere... so I've just changed it to 1 - that may help a little (or at least buy more time before it goes silly)

For some reason inside PDApp.log verbosity is defaulting to 4 - there should be some other magic xml value to be set in the prefs that will override that - but I can't find any reference to it anywhere and the XML for this file seems to be completely undocumented by Adobe (that I can find) - so if anyone else sees anything that would help at least reduce the verbosity of this stuff then please update this seems to be a common problem, and when AAM goes wrong (possibly when it can't reach Adobe CC - but I can't prove that) - these logs fill up quicker than you can blink.

Sorry for pointing it out Marc

Oh and for the record - it's nothing to do with Fireworks - its AAM so this thread is possibly in the wrong place

yup... there has to be a way of stopping this happening:

and there are a few tools out there that will help you find this sort of stuff (generally) - GrandPerspective (SourceForge) got me straight to the point:

...fairly obvious where the problem was...