Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

After waking from sleep vfp error "...pushjump / popjump call"

Status
Not open for further replies.

dkean4

Programmer
Feb 15, 2015
282
US
Lately, I get this error if I allow my current project to stay open and go to get a cup coffee. I wake up the PC and log back in and VFP has crashed giving me a warning about "...pushjump / popjump call". I looked for that error on the WEB and no cheese.

Has anyone encountered this problem before?

TIA

Dennis Kean

Simplicity is the extreme degree of sophistication.
Leonardo da Vinci
 
I remember this last was said about the bet version of VFP9 when waking up from hibernation.
Just don't let a VFP session hibernate is the best advice. Not everything VFP needs back to normal is in control of the VFP runtime, eg file handles.

Bye, Olaf.
 
I only have that issue with this one enormous project. None of the other projects do that.

So, you are saying that I should not let the PC go to sleep? Is there a way that I can fire up some app, while the VFP IDE is open, which will fake me using the keyboard and mouse? Or can I capture the hibernation event somehow, so I can trigger some mouse movement on it when my VFP IDE is open??


Dennis Kean

Simplicity is the extreme degree of sophistication.
Leonardo da Vinci
 
It's easier, you can go into energy saving options and turn off any hibernation.
On the other side, shut down VFP and restart.

Bye, Olaf.
 
Going to sleep" isn't the same as hibernation. "Going to sleep" simply puts the computer into standy-by. The various components slow down or stop, but a keystroke or mouse movement will wake the machine up.

Hibernation is closer to a full shut-down. The entire state of the system is saved to the hard drive first, and is then restored when when you restart the machine. Hibernation takes longer than stand-by, but has the advantage that it survives a power interruption.

You generally have to explicitly enable hibernation, and it is not necessarily supported on all machines (depends on available disk space and other factors).

Dennis, if you are just leaving the machine to get a cup of coffee, it's much more likely you are going into stand-by. But that doesn't explain the problem you are seeing. Sorry I can't suggest a solution.

Mike



__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads
 
Thanks for pointing out the difference of hibernation vs. sleep after a timeout or with keyboards having a special sleep (moon) key. I think the beta version problem also was about that normal sleep state and not only the hibernation "deep" sleep mode. So if that's still not fully fixed, the best idea still is to not leave VFP open, even in coffee breaks. The last hard problem of similar nature I had was about media change events I reacted to with bindevents. It did work in general, but explicitly failed on the notebooks a customer had already ordered in high numbers. We had to skip that feature to automatically react to media change events and instead use a timer polling DRIVETPYE().

I just bring this here, as you also might only have that problem in conjunction with your specific hardware. Which again just means avoid the problem. Turn up sleep times and put some things like hdd drives to a mode never going to sleep, which could help in case it's about behind the scenes used C++ filehandles for workareas becoming invalid. Not handles you have with FOPEN, but handles the VFP runtime has through USE or anything like that.

Bye, Olaf.
 
Mike,

Thanks for the explanation. I never needed to know that detail until today. My apps on VFP were never as big as this last one. I use up a lot of RAM on this project... text to speech with many voices multiple Databases, many and huge tables, many forms with graphic images, sounds and more ... Apparently, it adds up. I must have busted up one of the DBs with hibernation on the issues I had with the former call for help.
Now I have to get ready for my electric bill! Ha ha ha...

The good news is that I killed hibernation and no more trouble with crashes. So thanks again for your contribution.

Dennis Kean

Simplicity is the extreme degree of sophistication.
Leonardo da Vinci
 
Olaf,

As you specified, it was the hibernation issue. I killed it and no more crashes. I did not know the distinction between sleep and hibernation. Never needed to know. This project is huge, so it seems to matter. I never had this issue with other projects.

Thank you for your help.

Dennis Kean

Simplicity is the extreme degree of sophistication.
Leonardo da Vinci
 
Dennis

When your machine goes to sleep, does it throw up a screen saver? If so, silly as this may sound, it might be a dodgy print driver (yes, I said print in the same context as asking about screens) that is causing the issue - check your current ones are not doing anything unexpected. Modern drivers are very chatty with their targets and are often doing stuff that is covert.

Have a nice weekend.

Regards

Griff
Keep [Smile]ing

There are 10 kinds of people in the world, those who understand binary and those who don't.

I'm trying to cut down on the use of shrieks (exclamation marks), I'm told they are !good for you.
 
Griff

No, I learned that lesson years back. I removed the back image and have blanked out everything. A background image slows down the performance of the PC considerably. I assume that repainting windows over a background image takes more work, or whatever it is, it is the one imperative I stick to. Screensavers are not my ball of wax either for many reasons. Nevertheless, good ideas, Griff. Appreciate your thoughtfulness.


Dennis Kean

Simplicity is the extreme degree of sophistication.
Leonardo da Vinci
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top