My bad...VB6 infinite loop...

[Adam G]

Meh...I've been working for probably over 7 hours, I'd guess more like 8 1/2...jumping around a lot but working on my main project since before 10...
Anyway, screwed up and used this code...

Code: Select all

Do Until WebBrowser1.ReadyState = READYSTATE_COMPLETE
Loop
Call Grab

So...I'm sure you see the problem?
Yeah...it's running right now, seems to be keeping a quite steady rate of 50% CPU usage.

Is there any chance the code will go through? I'm all open to leave it running for some hours/days...


~Adam~

[marshallh]

Just hit Ctrl-Break.

[Adam G]

Just hit Ctrl-Break.

The post was at 4 AM, I've been getting very little sleep lately and basically just said screw it, I wasn't even thinking...
Thanks!


~Adam~

[timmeh87]

LOL classic.

[Skyone]

Haha! That's what you get for using VB6! Also, couldn't you have just gone into task manager?

[Adam G]

Haha! That's what you get for using VB6! Also, couldn't you have just gone into task manager?

Yes, I could have ended "form1" through the task manager, the problem being that form1 is considered the same process as Visual Basics, ending one would end both. My problem was, I hadn't saved the project since I opened it two days ago.

[marshallh]

Yea, I've done that too many times. The first time I wrote the main loop for GTP I forgot to put a DoEvents in the delay timing code.I pulled the plug on my machine, rebooted, and grabbed the source code out of the Temp folder. Saved a couple day's work.

[timmeh87]

Yeah ive done it too

[lifeisbetterwithketchup]

In VB.NET 2002, I know it's a separate process. You can kill it, and Visual Studio is still running, with all the source and stuff. It also saves your work when you compile. Guess that was a big improvement from VB6. It's saved my ass a few times.