[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Extremely wierd behaviour with default File->Quit
From:       Mantia Andras <amantia () freemail ! hu>
Date:       2002-08-31 9:02:01
[Download RAW message or body]

Try this in the slotFileQuit:

  if(memberList)
  {
    for(unsigned int i= 0; i< memberList->count(); i++)
    {
      memberList->at(i)->close();
    }
  }	

This works for me.

Andras

On Saturday 31 August 2002 11:29, Richard Garand wrote:
> I just noticed that my project starts to use up CPU time and allocate
> memory very fast when I use file->quit, which still uses the default code
> from KDevelop's KDE Normal application running on KDE 3.0.3. It enters an
> endless loop in slotFileQuit, at
>
> if(memberList)
>   {
>     for(w=memberList->first(); w!=0; w=memberList->first())
>     {
>       // only close the window if the closeEvent is accepted. If the user
> presses Cancel on the saveModified() dialog,
>       // the window and the application stay open.
>       if(!w->close())
> 	break;
>     }
>   }
>
> After about 2 minutes, top shows this for the process:
>
> 30004 richard   25   0  703M 393M  3460 R    85.1 78.2   1:10 kbudget
>
> I've tested this four times: with one open window, it closes and goes into
> this loop. With two open windows (in the same process), the second closes,
> the first freezes, and it goes in to this loop. With three open windows,
> the first closes and it goes in to the loop. With about ten open windows, I
> don't see any closing before it starts.
>
> Am I doing something wrong? Is there any more information I can provide to
> track down this problem?

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]