Ubuntu 10.04 Is Hit By Major X.Org Memory Leak

[kraftman]

I like Kubuntu but I wouldn't count on this too much...
They were releasing this distribution versions (older *buntus) in history with known bugs in kernel or Xorg before because of the strict release dates.

Yes, stupid deadline. However, I never had serious problems with *buntus, so maybe it will remain the same this time.

I'd rather wait for several months till they get everything right. This timed release is getting more and more ridiculous, previous releases were full of bugs

According to Ubuntu bug tracker there aren't too many bugs open.

[gordboy]

Redemption Is At Hand

From the ubuntu-dev mailing list -

"Thanks to the tireless investigations of Robert Hooker and Tormod Volden ..."

Well done guys. You may well have averted a disaster.

[vermaden]

I have a feeling that Ubuntu 10.04 is like a toy made of pieces of Lego.

Do not blaspheme, LEGO blocks were very solid

[yesterday]

Yea, but I'm curious to see how stable it is now that it comes out, especially on the server side.

Then why do you care about a GLX issue?

[lithorus]

From the Wiki :

This does not affect cards using proprietary drivers or not using DRI2 because it is specific to the glx module that the open drivers use.

So it doesn't affect all.

[Sharky]

Ubuntu

HI all


Ubuntu is somewhere in the mix.

To the left of me I hear newer, newer, its already out dated.

To the right of me I hear bugs, to many bugs, more testing, release to fast.

Up in front of me the TWOCLICKINMEMENOWNOWS say its to hard.

Behind me I hear, eh bloated.


Ubuntu is at it every day doing there GNU/Linux thing, there way. I respect that.
I don't respect FUD or drama.

Sharky

[FunkyRider]

I'd rather wait for several months till they get everything right. This timed release is getting more and more ridiculous, previous releases were full of bugs

[KDesk]

Ubuntu 10.04 Is Hit By Major X.Org Memory Leak

This way or writing sounds like Ubuntu 10.04 will be a broken release full of memory leaks. You can write a better title, like "Ubuntu 10.04 develoment/beta release is hit by major X.Org memory leak".

The problem would have been if the release the "stable" 10.04 with the memory leak. It is only a beta version, this is sometimes the price for using it.

The Ubuntu developers should use more Upstream stable code, and not take some more or less good known stable code and start to patch it, they will get less users and devs to test it.
Why did they not take the Xserver 1.8 code, release 10.04, and push updates with 1.8.1, and 1.8.2, etc. but only the 1.8.x serie. More or less as they do with the kernel?

[whiskey_tango]

Good thing they found out about this before release and are going to fix it. Of course that doesn't stop the Ubuntu haters from taking cheap shots at Ubuntu

Interesting because that's the first thing I thought too when I read the story.
Imagine fixing bugs Before releasing software. Good luck with that catching on.

[glasen]

Is this issue isolated to Ubuntu's hacked together hybrid of xorg-server 1.7.x and 1.8.x or does it affect upstream's sources too?

https://wiki.ubuntu.com/X/Testing/GEMLeak

One possible solution is to roll back the GLX 1.4 enablement patches, and the patch which caused the memory leak to appear. These GLX patches were produced by RedHat and incorporated into Debian, they were not brought in due to Ubuntu-specific requirements and thus it is believed dropping these patches would not impact any of Lucid's development goals. The one risk to be mindful of is if any userspace applications have come to depend on the newer GLX functionality.

http://packages.debian.org/changelogs/pool/main/x/xorg-server/xorg-server_1.7.6-2/changelog

xorg-server (2:1.7.3.901-1) experimental; urgency=low

[ Julien Cristau ]
* Enable GLX 1.4 on DRI2 and swrast (from upstream, via F12).

I hope this answers your question.