uses too many resources

[campbeld]

I am running Win98SE and First Page 2006 eats up computing resources and doesn't stop!!! It keeps gobbling resources until my computer crashes. Is there a memory leak somewhere? Does First Page release resources after it is done using them???

[Galactic]

I am running Win98SE and First Page 2006 eats up computing resources and doesn't stop!!! It keeps gobbling resources until my computer crashes. Is there a memory leak somewhere? Does First Page release resources after it is done using them???

Campbeld, the system requirement page at evrsoft.com for FP2006 (final). lists Windows ME as a version that will work, Windows 98SE is not named. One forum post says that Windows 98SE will work. Because Windows ME is not so different from Windows 98 and Windows 98SE is even more like Windows ME, I would expect that if the program can run under Windows ME that it would run under Windows 98SE.

This is a link to a thread that explains why I would not run a large application like FP2006 (final) under Windows ME or earlier.
http://developers.evrsoft.com/forum/showthread.php?p=23795#post23795

Even so, some running Windows XP there are many reports that FP2006 (final) has frequent freezes or abnormal termination when it is issued the File/Exit command. These terminations are usually accompanied by information messages that application caused an error and must close (or similar wording). If DEP is turned on for all programs, DEP message Windows also appears. These messages sound similar to the ones you are getting. If you were you running Windows XP at this moment you might be having the same / similar problem with FP2006 (final). This may mean that things that work to solve or mitigate the problems for those using Windows XP will work similarly for you.

Suggestions to help fix problems with FP2006 (final) are in the forums, usually as replies to threads asking for help. Often, the first poster responds that the suggestions helped.

In this thread,
http://developers.evrsoft.com/forum/showthread.php?t=4550
on the "general discussion" forum I discuss some things that may help. The post, edited twice now, incorporates all the experiences that I had found so far on the forums. The best experience I have read yet, is what forum member jon did.

Jon had tried everything he could think of and every suggestion he could find, and nothing had helped. Then he read my post and noticed a little thing. He, like me, thought that this thing mentioned there, while it was something extra that could be done, was unlikely to change anything. Even though skeptical, he tried it and it worked.

Jon’s post is classic. I “redirect” forum readers who come to my post on to his. I think what jon did is the first thing to do. If you try it, let us know what happens, either way.

[Terminator1138]

you can look in the program help area ..i think the about and it says how much memory is being used.... Win98 etc does not manage memory much so make sure you don't have other windows open also

[Galactic]

If you seem to be losing available memory and resources while working with FP final, open the Task Manager window (ctrl - alt - del), click on Process tab, click on "Image Name" column, this will sort your processes in alpha-numeric order of the process names, and see how many 1st page processes are shown. They should be together and at or near the top of the Task Manager process information pane.

There should be 1 1st Page process, if 1st page is open, and 1st Page process should not be running after FP is closed.

On one of PhantomII's PCs, he was gaining another running 1st page process every time he opened and closed the program.

If you had found that FP final has a memory or resource issue and now have found that it is leaving a process running, when closed, consider that good news. :confused: There seems to be a way to correct the problem of leaving processes open. PhantomII thinks that this may be what has been causing the several instances of a memory or resource problem reported on the forums.

A suggested solution for the problem, if it proves out, will be posted to the forum soon. The same solution seems to be a good workaround for two other often reported bugs. :)

In the meantime, use Task Manager to close the 1st page process(es) after you close the program, each time you use it. If you have used the program since your last PC boot up, but it is closed now, check with the Task Manager. If 1st Page processes are open, close then. I think that if FP ends abnormally (leaving a process running after close sounds abnormal), that changes made in the General Preferences menu and sub-menu may not be remembered on the next start. Otherwise, closing the process after closing the program is an immediate (temporary) patch to the memory / resource problem you were having.

Consider turning on DEP protection for all programs. DEP possibly will intervene and force FP to close, albeit with some message windows, if each time you are otherwise "closing" the program it remains an open process (according to Task Manager).

We do not know how often this problem is occurring. It has not been seen on all PCs checked. If you have the problem, reply to the linked thread. Your responses will give us some idea of how common this problem is. Mention if you have the remaining process problem, whether you had noticed a problem with memory or resources previously and tell us about your PC system including the Windows version.

The PhantomII thread on 1st Page processes that do not close is here,
http://developers.evrsoft.com/forum/showthread.php?t=4567

[Flying Dutchman]

I already made a suggestion to load only the modules that are really required to boot the program at start up and not to load modules that you most likely don't need (I, personally don't use design mode and write only HTML and occasionally some Javascripting.

These should be loaded when called upon; this takes some time then but prevent the slow loading of the program and hunger for resources. (remember OSA9.exe)

I haven't seen an answer yet to that suggestion... :verymad:

[Terminator1138]

Good idea on the module loading....would possible allow for more system specs to be added also like low end systems..
Lets hope you get an answer.

[Galactic]

FP final already is modular. When the Nag Screen is showing it uses about 20MB memory. When the main applicaiton is loaded is uses about 30MB memory. When you bring the Nag Screen back it uses about 20MB.This is true, but I am just joking about it being modular. :[added this paragraph and next by editj]


For some FP final initally uses about 30MB, later 60MB, still later 90MB and still later 120MB of RAM. No, this time I am not joking. This happened. Fortunately he was able to fix the problem. This may be happening to those complaining about the amount of resources and memory that FP final uses. The explanation of what happend is the subject of this post.

Here is what happened:

Open FP final.
Close FP final.
Look in Task Manager.One FP process running.
Open FP final
Close FP final
Look in Task Manager. Two FP process running, each same size.
Open FP final
Close FP final
Look in Task Manager. Three FP process running, each same size.

On the PC this happend on, Task Manager reports that there is one copy of FP final for for each time FP has been started since the last computer startup. If you think running FP takes a lot of memory and resources, think of how much 4 or more FP processes, running concurrently require. :(

FP always opening but never closing (although it seems to close) could be what is happening to the folks that are posting threads that FP final is a resource hog or a memory hog

How are we going to know?
When people think that FP final is gobbling up resources, they need to open Task Manger, click on the process tab, click on Name (to get all the 1st page processes at the same place, at top and see how many copies of FP they have running..

If FP is open, there should be 1 process. If FP is closed, there should not be a FP process.

Let’s see if we can find out how often this application fails to close when it seems to close. It disappears from view on the desktop environment, but according to Task Manager it is still running.

Please, if you think you have a resource problem, use Task Manager to see if processes are not closing.
If you have multiple instances of FP running, please report it.

More details, and a link, are in the previous post by Galactic in this thread..

The good news is it seems there us a solution, not yet posted because it is being verified. The same solution seems to address "Splash Screen Hangs on Open", and "FP Crashes on Close".

[BillSamuel]

It crashes without closing and re-starting in my XP machine with 2 GB RAM. It does this if I work in it for a fairly long time. Is it steadily grabbing more and more resources until it will crash any machine built, or what? Only solutions seem to be to close and re-open periodically, and to save frequently (always a good idea in any program).

[Galactic]

It crashes without closing and re-starting in my XP machine with 2 GB RAM. It does this if I work in it for a fairly long time. Is it steadily grabbing more and more resources until it will crash any machine built, or what? Only solutions seem to be to close and re-open periodically, and to save frequently (always a good idea in any program).
Bill, I recommend you begin by checking for the process staying open after "closing". If this is happening to you, the problem is cumulative. Everytime you close and reopen 1st Page you gain another copy running on the PC. You can use Task Manager to close the extra copies (not a solution but easier than rebooting). I think my other response to this thread has suggestions for what to do to fix the problem if you have it. Also, if you have it, please tell us all. It is hard to get anyone to check for this.