Is it normal to see FrameMaker.exe in the Task Manager (using 93K of memory) after I have exited FrameMaker 9? Is this what they call a memory leak?
> Is it normal to see FrameMaker.exe in the Task Manager (using 93K of memory) after I have exited FrameMaker 9?
I would say no, as I don't see it when I exit FM9 on Win7/64. If you have an icon on the start bar or in the system notification area, then there might be some optional launcher hanging around. What happens when you restart FM?
> Is this what they call a memory leak?
No. A memory leak has to do with the amount memory allocated to a process (or to multiple processes), that was not released when all processes using it were done with it. It is associated with either a running process, or a formerly running process, but is not easy to spot with Task Manager. It's a real problem for daemons that run continuously, never exit, and keep grabbing more and more VM, until Mr.Bill chokes, bluescreens, and dies.
This is definitely not right, but I don't know the answer. FM has the ability to hide the interface and continue running in the background, but normally this needs to be invoked by an API client. It should not happen from a normal exit. Do you have any weird clients or plugins running? An API client could intercept the close command and hide the interface instead, but I struggle to imagine why that would be useful.
In case this is helpful to anyone else, here is what I've learned. This is after many hours of troubleshooting and two calls (one a chat) to Adobe Support. I'll try to be concise.
First problem: Frame would not start. I could see FrameMaker.exe as a process in the task manager, but absolutely nothing on the screen. After quite a bit of investigation, the Adobe tech told me this is a problem with the Adobe licensing system. So we renamed a licensing folder. Now I can see Frame. I thought everything was fine.
Second problem: I notice if I start and close Frame, it's still running in the Task Manager (as shown in a previous post). If I start and close 3 times, I'll have 3 Frame processes running. The second Adobe tech checks many things (remotely) and tells me this is a result of the previous licensing fix (my first problem). Acrobat does the same thing--leaves one or multiple processes running after it's closed. The tech said this won't cause any problem and that I can ignore it. (It's true that Frame seems to work fine now.) But isn't this using/wasting memory I asked? No, because it's running "in the background." However, Task Manager says these processes are using memory. Also, I can't delete a folder that contains the Frame doc I last used. A message says it's being used. So I'm thinking the process is not letting go. But even after I end the process I can't delete this folder.
I agree with what Russ said above, "This is definitely not right." It seems there should be a better solution.
It seems this is all a result of a broken licensing system, and I am left with two Adobe applications that aren't behaving as they should. BTW, before I called Adobe the first time I ran an Adobe utility for "license recovery," but this did not fix the first problem (i.e, that Frame did not appear).
If that's the case, then there's something different in your machine from the others. You may end up having to get a new profile set up - that's been as source of FM issues before that I've read about.
Adobe was trying to help me with this problem, but I think they've given up. The Adobe Support Portal says my case is still open, but they haven't responded for about 3 weeks now.
Each day after using (and exiting) Frame and Acrobat I have to manually close the Frame and Acrobat processes. One Adobe tech said I could ignore them, but I don't think that's wise because multiple Frame and Acrobat processes will accumulate, and Task Manager says each one is using memory.
Thank you to forum members for your suggestions. It doesn't appear that others have had this problem or that anyone really knows a solution. It does seem likely that this is or is related to a Frame and Acrobat licensing problem.
The fact that it's only your machine displaying this persistence indicates that there's something different about your machine. What happens if one of your coworkers (or IT) logs into your machine and starts up FM? Do the exes still remain active after exiting? If they don't, then the culprit is a dodgy user profile; if they do, then there has to be something else going on on your machine that affects all users.
I don't recall if you gave us details of your o/s, but because the licensing issue seemed to be the cause of this persistence, I would start fresh - deactive, uninstall, get a new profile set up, reinstall FM, activate and you should be just like your coworkers.
I had fresh installed FrameMaker about 2 weeks ago, shortly after this mess started. Since Adobe told me this was an Adobe licensing problem, last week I uninstalled Frame AND Acrobat AND everything with Adobe in its name. Unfornately Acrobat would not uninstall through Add/Remove Programs or with the CD. So I had to manually uninstall it. The Adobe Tech told me to use the instructions for manual uninstall of Reader 8. I have Acrobat Pro 9. He said there are no manual uninstall instructions for Acrobat Pro 9. Should anyone be surprised that these instructions did not apply very well? I got Frame and Acrobat installed again. I still have processes that run when you close Frame or Acrobat.
Now I have Distiller doing the same thing. If I create a PDF through Frame (Save As PDF), Distiller shows in the Task Bar, but you can't open it. I can't create another PDF unless I kill Distiller first.
I think I will have to ask IT to re-image my computer. I hate to do this because it will mean at least 1 day of lost work, but I see no good alternative.
Thanks for your help, Jeff.
I'd try using a powerful uninstaller called revouninstaller - the free version works really well at rooting out all signs of a program. I've used it to clean up one of my machines and Peter Grainge over on the RH forum recommends it as well.
Europe, Middle East and Africa