PDA

View Full Version : More speed tests


WillyT
02-14-2003, 08:08 PM
I did some more slopy speed checks with glxgears.

The beta .2 of X11 is really fast.

Quartz-wm and enlightenment are now running neck and neck at about 480 to 510 fps.

One time I got a false reading of over 2000 fps. but it was obvious that stuff was'nt really updateing with the frozen graphic.

One problem I'm having is Buss Errors from enlightenment when I Quit X11. I normally logout of Gnome and that would quit XDarwin but X11 keeps on running. So I Quit from the menu and enlightenment just keeps putting out buss errors till I kill -9 pid. Huge crash logs with Console takeing all the cpu it can get.

I'll try rebuilding enlightment aginst the new X11 and see if that helps.

I have a Reason not to be grumpy.
Willy

Miga
02-19-2003, 03:05 PM
You should quit all applications, exit all xterms, quit your window manager before quitting X11.

WillyT
02-19-2003, 10:39 PM
Miga

I normally log out of Gnome-session but this isn't killing enlightenment. Today I saw enlightenment twice in top. Probably from switching to Quartz-wm and back in Gnome control center.

I don't have this problem starting from XDarwin. So its really all in the way X11 just keeps going after .xinitrc ends. Maybe something else in X11 not actually letting the wm know it is going away or something?

Willy

Miga
02-20-2003, 12:55 AM
Originally posted by WillyT
Miga

I normally log out of Gnome-session but this isn't killing enlightenment. Today I saw enlightenment twice in top. Probably from switching to Quartz-wm and back in Gnome control center.

I don't have this problem starting from XDarwin. So its really all in the way X11 just keeps going after .xinitrc ends. Maybe something else in X11 not actually letting the wm know it is going away or something?

Willy

The problem is how X11 launches, hence how it quits. It does not bother to launch the window manager in background, so that when it quits, it does not wait for its children to exit and that causes a lot of problems: zombies, bus errors, lock not unlocked, etc..

You can force it to do it by launching it from a script and telling it exactly what to do and then quitting as I told before.

Though I'm not sure how it can work in non rootless mode.