Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2002-10

Lazarus still freezes X

17 messages · 4 people ·

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Mattias Gaertner
to Mattias Gaertner: I heard that Lazarus still freezes X on some systems. Has anyone any idea what causes it?…
Show quoted text 7 lines
At 22:55 16-10-2002 +0200, Mattias Gaertner wrote: >Hi all, > >I heard that Lazarus still freezes X on some systems. >Has anyone any idea what causes it? I only see it when I'm debugging (debugging a debugger triggers it often)

Yes you mentioned this some time ago. But in this case the debugger is not involved.

Other reasons to lock is sometimes setting a breakpoint in a mouse event. That case looks to me that the (mouse ?) event handler is shared amoung all X apps. If you block that, all other apps freeze including X.

Whoa. That's interesting.
I knew that most of the reasons for an X freeze is an input grab, where the grabbing window is destroyed. But freezing by setting a breakpoint is something much more common. This is a simple OnMouseDown event with not much gtk involved. If it can be triggered that simple, then I wonder, why it does not appear more often. I will check the whole mouse grabbing code ...

I don't know if other events trigger this as wel. When I kill Lazarus throug the console, everything unfreezes

Sounds like we are loosing grab handles somewhere.

Mattias

Reply by email

Andrew Johnson
to Tony Maro: On the down side, it just froze on me... :-P I don't even have hints turned on. I…

FYI, the problem at this point is primarily MOUSE related.. aka all keyboard shortcuts as you noticed, work. So Lazarus shortcuts should work as well. This means that alt-tab'ing to the object-inspector or the like, and using alt-F will allow you too acces the menu and close program vi Quit.

Andrew

Tony Maro wrote 83 lines
On the down side, it just froze on me... :-P I don't even have hints turned on. I attempted a build on my app and the messages window showed an error so I clicked to jump to it and clicked the wrong one. So, I clicked right back in the messages window and after that nothing would take input except certain parts of Lazarus. Lazarus windows that were open would not raise to the top. I could alt-tab between windows, but clicking on the gnome-panel or attempting to close Lazarus would do nothing. I had to CTRL-ALT-F1 to console and killall lazarus to get control back. Sounds amazingly like what you guys have been describing and has never happened to me until today. My CVS sources were updated about 2 hours ago. -Tony -----Original Message----- From: Andrew Johnson Sent: Fri 10/18/2002 5:34 PM To: Cc: Subject: Re: [lazarus] Lazarus still freezes X On Fri, 18 Oct 2002 14:47:28 +0200 "Mattias Gaertner" wrote : >On Fri, 18 Oct 2002 08:12:18 -0400 >"Andrew Johnson" wrote: > > > >>On Thu, 17 Oct 2002 17:06:33 +0200 >>"Mattias Gaertner" wrote : >> >> >> >>>The problem is not, where it does _not_ freeze. I myself don't have >>>such a freezer. >>>The freezes appear on a RH7.3 to RH8.0 upgraded computer and with the >>> >>>current lazarus, the lazarus one month ago, but not the lazarus 2 >>>months ago. >>>So, this is probably something Andrew and I have done. >>> >>> >>Hmm, I just thought of something.. I had set Hint Window's to be >>transient to the main form, before I changed the BorderStyle code, but >>I never removed it when I was done. Since Hint Window's are still >>popup's..it is possible that they could get stuck recieving all >>Lazarus Mouse calls, though I thought this had been fixed, but if >>something in X or later versions of GTK has changed the behaviour of >>popup's this could have some deadly results. Try disabling the code >>that set hint windows transient for now. It is in the create routine.. >>I will look into making Hint windows Bordlerless Transient Dialogs >>instead on my system here and see how well that works. If it takes >>care of all the problems I will commit it and see what happens for >>other people using RH >=7.3 >> >> >I also thought so, but the hints were not created at all and it freezes. >I looked at the grabbing code in the gtk itself and found out, that the >old capturing code in the gtk interface did not really play nice >together with some of the gtk widgets. So, I completely rewrote the >capturing/uncapturing and now it seems to work ... time will show ... > > Well bright side.. I think, though I can't be positive yet, that at least the hintwindow errors on destroy widget are gone now. I think that transient windows are destroyed with the parent, so if hint windows still existed(had valid handles in memory).. we get invalid typecasts. Andrew _________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives

Reply by email

Andrew Johnson
Show quoted text 6 lines
The problem is not, where it does _not_ freeze. I myself don't have such a freezer. The freezes appear on a RH7.3 to RH8.0 upgraded computer and with the current lazarus, the lazarus one month ago, but not the lazarus 2 months ago. So, this is probably something Andrew and I have done.

Hmm, I just thought of something.. I had set Hint Window's to be transient to the main form, before I changed the BorderStyle code, but I never removed it when I was done. Since Hint Window's are still popup's..it is possible that they could get stuck recieving all Lazarus Mouse calls, though I thought this had been fixed, but if something in X or later versions of GTK has changed the behaviour of popup's this could have some deadly results. Try disabling the code that set hint windows transient for now. It is in the create routine.. I will look into making Hint windows Bordlerless Transient Dialogs instead on my system here and see how well that works. If it takes care of all the problems I will commit it and see what happens for other people using RH >=7.3

Andrew

_________________________________________________________________ Surf the Web without missing calls!�Get MSN Broadband. http://resourcecenter.msn.com/access/plans/freeactivation.asp

Reply by email

Andrew Johnson
Show quoted text 22 lines
On Thu, 17 Oct 2002 17:06:33 +0200 "Mattias Gaertner" wrote : >The problem is not, where it does _not_ freeze. I myself don't have such a >freezer. >The freezes appear on a RH7.3 to RH8.0 upgraded computer and with the >current lazarus, the lazarus one month ago, but not the lazarus 2 months >ago. >So, this is probably something Andrew and I have done. Hmm, I just thought of something.. I had set Hint Window's to be transient to the main form, before I changed the BorderStyle code, but I never removed it when I was done. Since Hint Window's are still popup's..it is possible that they could get stuck recieving all Lazarus Mouse calls, though I thought this had been fixed, but if something in X or later versions of GTK has changed the behaviour of popup's this could have some deadly results. Try disabling the code that set hint windows transient for now. It is in the create routine.. I will look into making Hint windows Bordlerless Transient Dialogs instead on my system here and see how well that works. If it takes care of all the problems I will commit it and see what happens for other people using RH >=7.3

Well I checked it out.. and while the transient popup code was causing problems, after removing it I still have occasional lazarus lock-ups on RH 7.3, so I am guessing that it may still lock-up RH 8,though I don't have it yet to test. I tried switching to borderles dialogs,and it worked, however it caused the WM to try and show it as a dialog.. aka sound affects if enabled, show's up in the task bar etc. I will try and work around that if possible, but for the moment I am clueless as to how.

Andrew

_________________________________________________________________ Surf the Web without missing calls! Get MSN Broadband. http://resourcecenter.msn.com/access/plans/freeactivation.asp

Reply by email

Tony Maro

On the down side, it just froze on me... :-P

I don't even have hints turned on.

I attempted a build on my app and the messages window showed an error so I clicked to jump to it and clicked the wrong one. So, I clicked right back in the messages window and after that nothing would take input except certain parts of Lazarus. Lazarus windows that were open would not raise to the top. I could alt-tab between windows, but clicking on the gnome-panel or attempting to close Lazarus would do nothing. I had to CTRL-ALT-F1 to console and killall lazarus to get control back.

Sounds amazingly like what you guys have been describing and has never happened to me until today. My CVS sources were updated about 2 hours ago.

-Tony

Earlier message 63 lines
-----Original Message----- From: Andrew Johnson Sent: Fri 10/18/2002 5:34 PM To: Cc: Subject: Re: [lazarus] Lazarus still freezes X On Fri, 18 Oct 2002 14:47:28 +0200 "Mattias Gaertner" wrote : > >On Fri, 18 Oct 2002 08:12:18 -0400 >"Andrew Johnson" wrote: > > > On Thu, 17 Oct 2002 17:06:33 +0200 > > "Mattias Gaertner" wrote : > > > > >The problem is not, where it does _not_ freeze. I myself don't have > > >such a freezer. > > >The freezes appear on a RH7.3 to RH8.0 upgraded computer and with the > > > > > >current lazarus, the lazarus one month ago, but not the lazarus 2 > > >months ago. > > >So, this is probably something Andrew and I have done. > > > > Hmm, I just thought of something.. I had set Hint Window's to be > > transient to the main form, before I changed the BorderStyle code, but > > I never removed it when I was done. Since Hint Window's are still > > popup's..it is possible that they could get stuck recieving all > > Lazarus Mouse calls, though I thought this had been fixed, but if > > something in X or later versions of GTK has changed the behaviour of > > popup's this could have some deadly results. Try disabling the code > > that set hint windows transient for now. It is in the create routine.. > > I will look into making Hint windows Bordlerless Transient Dialogs > > instead on my system here and see how well that works. If it takes > > care of all the problems I will commit it and see what happens for > > other people using RH >=7.3 > >I also thought so, but the hints were not created at all and it freezes. >I looked at the grabbing code in the gtk itself and found out, that the >old capturing code in the gtk interface did not really play nice >together with some of the gtk widgets. So, I completely rewrote the >capturing/uncapturing and now it seems to work ... time will show ... Well bright side.. I think, though I can't be positive yet, that at least the hintwindow errors on destroy widget are gone now. I think that transient windows are destroyed with the parent, so if hint windows still existed(had valid handles in memory).. we get invalid typecasts. Andrew _________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives <<winmail.dat>>

Reply by email

Mattias Gaertner
to Marc Weustink: I only see it when I'm debugging (debugging a debugger triggers it often) Other reasons…
Well I must admit this is one bug I haven't seen. Whew - at least nobody's going to ask me for source code to reproduce it! ;-)

;)
Your last bug sources were very helpful.

The problem is not, where it does _not_ freeze. I myself don't have such a freezer. The freezes appear on a RH7.3 to RH8.0 upgraded computer and with the current lazarus, the lazarus one month ago, but not the lazarus 2 months ago. So, this is probably something Andrew and I have done.

Mattias

Reply by email

Mattias Gaertner
to Andrew Johnson: On Thu, 17 Oct 2002 17:06:33 +0200 Hmm, I just thought of something.. I had set Hint…
Show quoted text 23 lines
On Thu, 17 Oct 2002 17:06:33 +0200 "Mattias Gaertner" wrote : >The problem is not, where it does _not_ freeze. I myself don't have >such a freezer. >The freezes appear on a RH7.3 to RH8.0 upgraded computer and with the > >current lazarus, the lazarus one month ago, but not the lazarus 2 >months ago. >So, this is probably something Andrew and I have done. Hmm, I just thought of something.. I had set Hint Window's to be transient to the main form, before I changed the BorderStyle code, but I never removed it when I was done. Since Hint Window's are still popup's..it is possible that they could get stuck recieving all Lazarus Mouse calls, though I thought this had been fixed, but if something in X or later versions of GTK has changed the behaviour of popup's this could have some deadly results. Try disabling the code that set hint windows transient for now. It is in the create routine.. I will look into making Hint windows Bordlerless Transient Dialogs instead on my system here and see how well that works. If it takes care of all the problems I will commit it and see what happens for other people using RH >=7.3

I also thought so, but the hints were not created at all and it freezes. I looked at the grabbing code in the gtk itself and found out, that the old capturing code in the gtk interface did not really play nice together with some of the gtk widgets. So, I completely rewrote the capturing/uncapturing and now it seems to work ... time will show ...

Mattias

Reply by email

Mattias Gaertner
to Mattias Gaertner: I heard that Lazarus still freezes X on some systems. Has anyone any idea what causes it?…
Show quoted text 15 lines
On Thu, 17 Oct 2002 12:41:30 +0200 Marc Weustink wrote: > At 22:55 16-10-2002 +0200, Mattias Gaertner wrote: > >Hi all, > > > >I heard that Lazarus still freezes X on some systems. > >Has anyone any idea what causes it? > > Other reasons to lock is sometimes setting a breakpoint in a mouse > event. That case looks to me that the (mouse ?) event handler is > shared amoung all X apps. If you block that, all other apps freeze > including X. Sounds like we are loosing grab handles somewhere.

I have added some more restrictions and checks for mouse capturing. Hopefully this does not break any special widget.

Mattias

Reply by email

Andrew Johnson
Show quoted text 33 lines
On Fri, 18 Oct 2002 08:12:18 -0400 "Andrew Johnson" wrote: > On Thu, 17 Oct 2002 17:06:33 +0200 > "Mattias Gaertner" wrote : > > >The problem is not, where it does _not_ freeze. I myself don't have > >such a freezer. > >The freezes appear on a RH7.3 to RH8.0 upgraded computer and with the > > > >current lazarus, the lazarus one month ago, but not the lazarus 2 > >months ago. > >So, this is probably something Andrew and I have done. > > Hmm, I just thought of something.. I had set Hint Window's to be > transient to the main form, before I changed the BorderStyle code, but > I never removed it when I was done. Since Hint Window's are still > popup's..it is possible that they could get stuck recieving all > Lazarus Mouse calls, though I thought this had been fixed, but if > something in X or later versions of GTK has changed the behaviour of > popup's this could have some deadly results. Try disabling the code > that set hint windows transient for now. It is in the create routine.. > I will look into making Hint windows Bordlerless Transient Dialogs > instead on my system here and see how well that works. If it takes > care of all the problems I will commit it and see what happens for > other people using RH >=7.3 I also thought so, but the hints were not created at all and it freezes. I looked at the grabbing code in the gtk itself and found out, that the old capturing code in the gtk interface did not really play nice together with some of the gtk widgets. So, I completely rewrote the capturing/uncapturing and now it seems to work ... time will show ...

Well bright side.. I think, though I can't be positive yet, that at least the hintwindow errors on destroy widget are gone now. I think that transient windows are destroyed with the parent, so if hint windows still existed(had valid handles in memory).. we get invalid typecasts.

Andrew

_________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

Reply by email

Tony Maro
to Marc Weustink: I only see it when I'm debugging (debugging a debugger triggers it often) Other reasons…

Well I must admit this is one bug I haven't seen. Whew - at least nobody's going to ask me for source code to reproduce it! ;-)

Just so you have a baseline, here's my system that's NOT experiencing this:

Recent install of Mandrake 8.2 running Gnome but with KDE installed All recommended updates from red-carpet
P4 2 GHz 1 GB RAM on a SOYO Dragon MOBO
Voodoo3 video card (my Radeon 7500 worked for about a week and then would cause lockups in both Winblows and Linux - swapped with another computer and it works in his - but I got the crappy Voodoo 3) HP wireless mouse configured using "MouseManPlusPS/2" on /dev/psaux

gnome-core 1.4.1-1.ximian.5
libgtk+1.2 1.2.10-25.ximian.31
libgtk+2 1.3.13-2mdk
Sawfish-1.0-9.ximian.6

And my other system NOT experiencing this is:
Mandrake 8.2 as well with same exact packages as above Abit KT7A-RAID MOBO
1.2 GHz AMD Athlon
Geforce2 MX 400 with TV out running true nVidia driver SoundBlaster PCI 512 sound card
Memorex wireless optical mouse configured using "IMPS/2" on /dev/psaux

Hope that helps...

-Tony

Reply by email

Tony Maro

Aha - I guess I should learn to use keyboard shortcuts just in case... LOL

But what I found MOST interesting was that it had never happened to me before tonight, and it happend three times in two hours. Did someone add a patch today that perhaps made things worse while trying to fix it?

-Tony

Earlier message 16 lines
-----Original Message----- From: Andrew Johnson Sent: Fri 10/18/2002 8:25 PM To: Cc: Subject: Re: [lazarus] Lazarus still freezes X FYI, the problem at this point is primarily MOUSE related.. aka all keyboard shortcuts as you noticed, work. So Lazarus shortcuts should work as well. This means that alt-tab'ing to the object-inspector or the like, and using alt-F will allow you too acces the menu and close program vi Quit. Andrew <<winmail.dat>>

Reply by email

Mattias Gaertner
to Mattias Gaertner: On Thu, 17 Oct 2002 12:41:30 +0200 Yes you mentioned this some time ago. But in this case…
Show quoted text 35 lines
At 18:49 17-10-2002 +0200, Mattias Gaertner wrote: >On Thu, 17 Oct 2002 16:30:01 +0200 >Mattias Gaertner wrote: > > > On Thu, 17 Oct 2002 12:41:30 +0200 > > Marc Weustink wrote: > > > > > At 22:55 16-10-2002 +0200, Mattias Gaertner wrote: > > > >Hi all, > > > > > > > >I heard that Lazarus still freezes X on some systems. > > > >Has anyone any idea what causes it? > > > > > > Other reasons to lock is sometimes setting a breakpoint in a > > > mouse event. That case looks to me that the (mouse ?) event > > > handler is shared amoung all X apps. If you block that, all > > > other apps freeze including X. > > > > Sounds like we are loosing grab handles somewhere. > >I have added some more restrictions and checks for mouse capturing. >Hopefully this does not break any special widget. I remember something that a scrollbar has some troubles as well. Not freezing, but grabbing all input, so lazarus seems irresponsive. I've seen this with other gtk apps as wel so I guess it is a gtk issue. When you are tracking a scrollbar using the thumb and you move your mouse sideways from it, sometimes the thumb misses the event that you're not tracking it anymore and is stays focused. I can imagine that if such window is destroyed, everything freezes. . . . I said imagine, since if it is the case, it is a BadDesign (tm) of GTK.

Might be. But since there is only one user with this problem, I doubt, that this is the error I'm searching. He has already bounded it to somewhere around my vacation.

Mattias

Reply by email

Marc Weustink
to Mattias Gaertner: On Thu, 17 Oct 2002 12:41:30 +0200 Yes you mentioned this some time ago. But in this case…
Mattias Gaertner wrote 21 lines
On Thu, 17 Oct 2002 16:30:01 +0200 Mattias Gaertner wrote: > On Thu, 17 Oct 2002 12:41:30 +0200 > Marc Weustink wrote: > > > At 22:55 16-10-2002 +0200, Mattias Gaertner wrote: > > >Hi all, > > > > > >I heard that Lazarus still freezes X on some systems. > > >Has anyone any idea what causes it? > > > > Other reasons to lock is sometimes setting a breakpoint in a mouse > > event. That case looks to me that the (mouse ?) event handler is > > shared amoung all X apps. If you block that, all other apps freeze > > including X. > > Sounds like we are loosing grab handles somewhere. I have added some more restrictions and checks for mouse capturing. Hopefully this does not break any special widget.

I remember something that a scrollbar has some troubles as well. Not freezing, but grabbing all input, so lazarus seems irresponsive. I've seen this with other gtk apps as wel so I guess it is a gtk issue. When you are tracking a scrollbar using the thumb and you move your mouse sideways from it, sometimes the thumb misses the event that you're not tracking it anymore and is stays focused.
I can imagine that if such window is destroyed, everything freezes. .
.
.
I said imagine, since if it is the case, it is a BadDesign (tm) of GTK.

Marc

Reply by email

Marc Weustink
to Mattias Gaertner: I heard that Lazarus still freezes X on some systems. Has anyone any idea what causes it?…
Mattias Gaertner wrote
Hi all, I heard that Lazarus still freezes X on some systems. Has anyone any idea what causes it?

I only see it when I'm debugging (debugging a debugger triggers it often) Other reasons to lock is sometimes setting a breakpoint in a mouse event. That case looks to me that the (mouse ?) event handler is shared amoung all X apps. If you block that, all other apps freeze including X.

I don't know if other events trigger this as wel.

When I kill Lazarus throug the console, everything unfreezes

Marc

Reply by email

Andrew Johnson
to Tony Maro: Aha - I guess I should learn to use keyboard shortcuts just in case... LOL But what I…

Well it has definately started getting worse for me.. Lazarus hasn't froze up completly on me since upgrading but the mouse is giving me constant headaches, where all of a sudden I can no longer select things or click buttons on certain forms, unless I do a modal form like find, or close and reopen first. I am guessing that Mattias' new changes to this code is causing other problems, either in flawed existing code, or something else. I can't seem to find the problem, so I am leaving it up to him or someone else to figure out. fiddle-sticks.. I despise not knowing how to fix things.

Andrew

Tony Maro wrote 24 lines
Aha - I guess I should learn to use keyboard shortcuts just in case... LOL But what I found MOST interesting was that it had never happened to me before tonight, and it happend three times in two hours. Did someone add a patch today that perhaps made things worse while trying to fix it? -Tony -----Original Message----- From: Andrew Johnson Sent: Fri 10/18/2002 8:25 PM To: Cc: Subject: Re: [lazarus] Lazarus still freezes X FYI, the problem at this point is primarily MOUSE related.. aka all keyboard shortcuts as you noticed, work. So Lazarus shortcuts should work as well. This means that alt-tab'ing to the object-inspector or the like, and using alt-F will allow you too acces the menu and close program vi Quit. Andrew

Reply by email

Mattias Gaertner
to Tony Maro: Aha - I guess I should learn to use keyboard shortcuts just in case... LOL But what I…
Show quoted text 9 lines
Well it has definately started getting worse for me.. Lazarus hasn't froze up completly on me since upgrading but the mouse is giving me constant headaches, where all of a sudden I can no longer select things or click buttons on certain forms, unless I do a modal form like find, or close and reopen first. I am guessing that Mattias' new changes to this code is causing other problems, either in flawed existing code, or something else. I can't seem to find the problem, so I am leaving it up to him or someone else to figure out. fiddle-sticks.. I despise not knowing how to fix things.

Yes, I'm sorry. Tricky gtk has fouled me. Sometimes gtk releases a mouse grab, without noticing X. I have disabled mouse capturing and will read some more gtk code to find out, why gtk does so.
The old code didn't always release a mouse grab and so this bug never appeared before.

Mattias

Show quoted text 37 lines
Andrew Tony Maro wrote: > Aha - I guess I should learn to use keyboard shortcuts just in > case... LOL > > But what I found MOST interesting was that it had never happened to > me before tonight, and it happend three times in two hours. Did > someone add a patch today that perhaps made things worse while > trying to fix it? > > -Tony > > > > -----Original Message----- > From: Andrew Johnson > Sent: Fri 10/18/2002 8:25 PM > To: > Cc: > Subject: Re: [lazarus] Lazarus still freezes X > FYI, the problem at this point is primarily MOUSE related.. aka all > keyboard shortcuts as you noticed, work. So Lazarus shortcuts should > work as well. This means that alt-tab'ing to the object-inspector or > the like, and using alt-F will allow you too acces the menu and > close program vi Quit. > > Andrew > _________________________________________________________________ To unsubscribe: mail with "unsubscribe" as the Subject archives at http://www.lazarus.freepascal.org/mailarchives

Reply by email