Board index » off-topic » Re: Thread : freezing app.

2005-02-15 06:22:52 AM
off-topic18
what. If the main-thread drawing rate was the holdup, I would expect the
CPU to be pegged at the end-stop.
Rgds,
Martin
 

Martin James wrote:
 

disconnect before you can connect again.
Rgds,
Martin
PS I posted the demo app at last, but you've probaly written your stuff by
now.
Rgds,
Martin
 

{smallsort}

Martin James wrote:
its essential why does the component not do it for itself on
disconnection..
I have got and am going to have a look, thank you kindly so much for
your help.
 

Martin James wrote:
same deal, but it works fine with a memo, thus proving the ever
{*word*99}ness of me. Problem is, I havent found a good vt100 component that
does all I need thats free... and this one is great except under heavy
load (I didnt write it all, I did however make a lot of it, and a large
number of alterations to it)
 

Martin James a écrit :
I understand that using postMessage is the good way to communicate and I
definitely would use it in my further apps and modify the current one as
soon as possible.
Yet sorry if I'm a little stubborn, but I really would like to
*understand* why my current app freezes !
Is it my fault ? Is it the PC fault ? is it the Windows fault ? is it
the Delphi fault ?
As a thread newbie I would definitely say that it is my fault ... but I
can't figure out where is the problem.
And I can't understand why the app works on every single PC where I
tested it except one and only one where it freezes. I would say even
more : on the PC where it freezes it only freezes with XP !
I formated the PC installed win2k and it works !
I re-formated the PC installed XP and it freezes !
On other XP PC it works !
Help Mulder & Scully where are you ? ;-P
 

"Galadriel" < XXXX@XXXXX.COM >skrev i en meddelelse
I tried the app on my XP and let it run for about 6 minutes. No freeze.
Thoughts:
You are constantly adding lines to the memo, so the contents grow all the
time. Could the huge amount of data in the memo be the reason?
Or is there a difference on your XP and others XP where it works?
I'm thinking about different windows updates and security patches.
Could it be that the XP that freezes do not have all patches installed?
 

I wuld not like to advise on terminals/emulators - I've never written one.
In the othe, more complex, demo, I used the Async Pro terminal & emulator.
This is now free, AFAIK, on SourceForge. Maybee is lacks some funtionality
or is slow anyway.
Rgds,
Martin
 

app I do not know. It's not like the app is paging in and out and/or
flushing caches on a multiprocessor system. Besides, IMHO the kernel on XP
& W2k is the same, so I do not know how one OS could expoit a hardware
deficiency & the other not.
Very X.
not buying another one).
Rgds,
Martin
 

Finn Tolderlund wrote:
C:\ :) placing the items in a listbox, even setting the capacity to
like 300k+ it only processed around 5k of lines before seemingly
stopping.. it seems the messages are just flooding in and drowing in
out everything else..
 

Martin James wrote:
[snip]
How about faulty driver software?
This could also very well cause a freeze in the application.
Mainboard memory controller drivers and video card drivers come to mind.
I'd check that first before blaming it on the hardware itself.
There's many a driver delivered in Windows XP by Microsoft that will
cause bad things.
Also i experenced sometimes USB devices like memory sticks will hang
applications for no apparent reason..
 

Finn Tolderlund a écrit :
more time to freeze ... but the real app will freeze after less than a
minute so there is not a huge amoun of data in the TMemo.
doesn't freeze.
Thank you.
 

doesn't hang the app.
 

Martin James a écrit :
same way ? Could it be possible that XP handling the multithreading will
hit some instructions in the CPU that are bugged on the faulty machine
and Win2k will not ?
Or maybe some drivers are not the same between 2k and XP ?
Regards.
 

Marco Caspers a écrit :
memory controller ?