Question

i have a simple program that sorts a text file according to length of words per line
this program works without problems in my xp based old machine
now i run this program on my new win7/intel core i5 machine, it freezes whole system and back normal after it finishes it’s work.

i’v invastigated the code and found the line causing the freeze

it was this specific line…

caption := IntToStr(i) + '..' + IntTostr(ii);

i’v changed it to

 caption :=   IntTostr(ii);  //slow rate change

and there is no freeze

and then i’v changed it to

caption :=   IntTostr(i);  //fast rate change

and it freeze again

my procedure code is

 var tword : widestring;
      i,ii,li : integer;
 begin   
     tntlistbox1.items.LoadFromFile('d:\new folder\ch.txt');
     tntlistbox2.items.LoadFromFile('d:\new folder\uy.txt');
     For ii := 15 Downto 1 Do //slow change
      Begin
        For I := 0 To TntListBox1.items.Count - 1 Do //very fast change
        Begin     
          caption := IntToStr(i) + '..' + IntTostr(ii); //problemetic line               
          tword := TntListBox1.items[i];
          LI := Length(tword);
          If lI = ii Then
          Begin             
            tntlistbox3.items.Add(Trim(tntlistbox1.Items[i]));
            tntlistbox4.items.Add(Trim(tntlistbox2.Items[i]));
          End;
        End;
      End;
    end;

any idea why ? and how to fix it?
i use delphi 2007/win32

Answer 1

Is this happening inside an event handler on a form? I’m going to guess taht it is. In that case, “Caption” is in the scope of the form. The form’s caption text isn’t managed by the VCL, but by Windows, and if you’re sending a new WM_SETTEXT message on every iteration of the loop.

A thorough explanation of why this is doing what it’s doing would require knowledge of Windows internals that I don’t have, but if I were to take a guess, I’d say it’s something like this:

Every time you send that WM_SETTEXT message with a new caption, Windows checks to make sure it’s not identical to the existing caption. If it is, it can exit immediately. That’s why the infrequent change (the one that only uses ii) doesn’t slow your system down. But if it does change on every iteration, then Windows has to perform some sort of task switch in order to change it.

As for why that would bog down the entire system under a Vista kernel (including Win7) but not XP, that’s completely outside my area of expertise. But if you’re trying to do this as some sort of progress indicator, there are better ways, especially if this loop is as tight as it looks.

The best way to handle progress updates in a tight loop is to count iterations and only fire once every X times. (100 or 1000 can be good values for X, depending on how many times it’s running and how fast the whole thing takes.) This is basically what the ii only option does. You could also try putting a Progress Bar on the form to measure progress instead of doing it through the form’s caption.