Skip navigation
Currently Being Moderated

FM.exe keeps running

Jun 12, 2012 12:12 PM

Tags: #framemaker_9

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?

 
Replies
  • Currently Being Moderated
    Jun 12, 2012 12:39 PM   in reply to Bill at HNS

    > 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.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 12, 2012 1:08 PM   in reply to Error7103

    I wonder if the OP is seeing the FM Console still running? BTW - supposedly FM9 did have issues with memory leaks that have been fixed by FM10.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 13, 2012 5:19 AM   in reply to Bill at HNS

    Bill,

     

    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.

     

    Russ

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 13, 2012 6:51 AM   in reply to Bill at HNS

    Do you run in a "tight" environment - lots of security restrictions, rights, etc.? That might have something to do with the licensing system flailing away.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 13, 2012 7:35 AM   in reply to Bill at HNS

    That's probably the source of your grief (unfortunately)

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 13, 2012 8:16 AM   in reply to Bill at HNS

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 13, 2012 12:18 PM   in reply to Bill at HNS

    Yes, sometimes a corrupted user account causes issues. Then the IT admin comes along and sets them up with a new profile & all their issues go away.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 15, 2012 8:08 AM   in reply to Bill at HNS

    I don't remember - did you have any plug-ins or Framescript running?

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 11, 2012 6:29 AM   in reply to Bill at HNS

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 11, 2012 8:48 AM   in reply to Bill at HNS

    So there's got to be something different about your install of FM. I'd do the fresh install.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 16, 2012 12:55 PM   in reply to Bill at HNS
     
    |
    Mark as:
  • Currently Being Moderated
    Jul 16, 2012 1:45 PM   in reply to Bill at HNS

    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.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points