Since my PC died I'm using a PIII @ 800 mhz with only 256 MB of RAM.
I can't compile my app anymore because I keep getting this error.
PureBasic IDE wrote:---------------------------
PureBasic Debugger
---------------------------
The debugged executable did not respond to communication for 5 seconds. Disconnecting.
---------------------------
OK
---------------------------
Can you make the timeout longer in a future release? At least 10 seconds?
I compile using 5.31 (x86) on Win 7 Ultimate (64-bit).
"PureBasic won't be object oriented, period" - Fred.
eesau wrote:Or perhaps an option to set the timeout length yourself.
Yes, that would be nice.
I use a HIPS (Host Intrusion Prevention System) and when a new exe is launched for the first time I have to authorize it, there is some time involved in the process and so I usually get the timeout error and need to restart the debug session.
Yes, it takes longer than 5 seconds after the executable has been created and
the debugger is waiting for the created executable to start. Even more so if
other apps are running, but that's not always the case. I know people might
say that PureBasic shouldn't support such a low-end PC, but that's not fair.
Anyone's fast PC can break down at any time (like mine!) and you have to
use whatever you can get your hands on in the meantime.
I compile using 5.31 (x86) on Win 7 Ultimate (64-bit).
"PureBasic won't be object oriented, period" - Fred.
If your application is slow to start it's most likely your hard drive is taking too long to read the program into memory. I used to own a Pentium 3 933mhz and I don't consider that kind of a system slow at all, unless you're trying to run Vista on it or something.
Since upgrading to version 4.3, I too am experiencing this problem. Everything was fine prior to the version upgrade. I don't think it is related to my hard disk or processor speed. I have noted that my Kaspersky Internet Security pops up a message up stating PureBasic Compilation0.exe has been placed in group Low Restricted, just prior to the error dialog box. I was wondering if there was any update with this problem.
> If your application is slow to start it's most likely your hard drive is
> taking too long to read the program into memory
The compile/run thing is what's failing. Built executables run without problem.
Compile/run is slow, especially when other apps are running, so it's like the
CPU is struggling to juggle all system processes.
Five seconds is too short for a timeout for anything. Ten seconds is a better
minimum for anything, not just this issue. Just because today's PC are fast
doesn't mean the timeout should be dropped so low as to be unreliable.
I compile using 5.31 (x86) on Win 7 Ultimate (64-bit).
"PureBasic won't be object oriented, period" - Fred.
Me too, I vote for "customizable timeout" due to my old hardware.
Most of the time five seconds are enough for my system but some times the error does occur. Chance gets worse if many applications are running and/or working in the background.
This gets my vote too. I'm currently compiling over a slow internet connection using a slow network drive and every compiled app takes about 10 - 15 secs to start up. Maybe a 'Do you want to wait another 5 seconds?' requester would do the job.
