29 votes81 comments · Acrobat for Windows and Mac » Installation and Licensing · Flag idea as inappropriate… · Admin →
Thanks for the update Jan. Glad to know that your problem is resolved.
So far after a week with the new user login, I havent had to quit acrobat. It has had its usual share of crashes but not due to the memory issues.
I think creating a new user has definately helped me.
And I accidentally logged into the old user, with the updated software on monday and acrobat crashed again about half an hour later, so the update didnt do a thing
So I have finally been able to create a new user and get everything working as per my old user (mail, all my software, logins etc), and so far ***touch wood*** after two days I have yet to have a crash in acrobat.
I am hopeful, but I have had others try this and still had the same issue eventually start up again... I really dont want to be doing this every few months.
After speaking to Adobe support, I am going to try logging in to the computer using a different log in... of course that means setting up a completely new user with all the access to software i currently need... bit of a major effort.
So far it seems to be working but I have yet to set up the user as i need it to be for me to use, i.e email etc, so once i have done that and run for a few days, I will report back.
Someone else through work suggested it may be something in the current users library (i.e. something conflicting with acrobat that is causing the issue/conflict), so setting up a new user could fix it.
will see if it works ;-)
Not sure why Adobe support hasn't come back to suggest this if this does fix the issue??
LOL Harold I like your style!
I think I might give it a go as well... at least send them the thread through the customer service chat anyway... maybe many times!
so its been a year since this started, and as usual ADOBE are just ignoring it, maybe hoping it will go away?
Its been 'Under review' since november 2017
Its really f**ing frustrating to have to monitor ram usage this closely simply due to one application and then quit every hour (at the least) just to avoid a complete shutdown.
Is anyone at ADOBE even remotely interested that you have numerous peed off people??
I have also updated to High Sierra and still have the same ongoing issue.... Cmon Adobe, are you doing anything at all about this?
Hi again Adobe... anything? anything at all??
Its been 10 months since this issue started happening and it still continues, with nothing from Adobe to solve it.
yet again i am asking for a response from adobe!!
Its been 6 months now, I have restarted acrobat at least 15 times today after only 5 hours, plus a couple of restarts when the Ram has overloaded and forced me to restart.... this is driving me insane!
Not to mention slowing production down. Does adobe actually want to fix this issue?
Thanks for that Harold. Adobe has responded here but not for several months now, might have to post on the other thread as well!
and following up again... 6 months since it first appeared ADOBE, c'mon let us know if you are taking this seriously or just brushing it under the rug?
Once again, I'm asking any progress on this?
Its been almost three months since it started happening, september 1st 2017, and no solutions given yet, except for quitting the software often to avoid it crashing the computer.
Hi there, any progress on this?
Jan's suggestion doesnt help those of us with a later and full (not trial) version of pitstop 17. I have tried a clean install of Pitstop as well, but no difference to acrobat RAM usage, whether pitstop is running or not
The specs of mine are:
iMac (Retina 5K, 27-inch, Late 2014), 4 GHz intel core 17, 16 GB 1600 Mhz DDR3,
Acrobat Pro DC Build: 17.12.20098.240878, also with Pitstop pro 17
Running Yosemite 10.10.5Gwenda shared this idea ·
23 votesUnder review · 28 comments · Acrobat for Windows and Mac » Other · Flag idea as inappropriate… · Admin →Gwenda supported this idea ·
Hi there, this is the same as this thread
and we are still waiting for some result from adobe? Its been almost 6 months since this started happening