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

List:       kde-core-devel
Subject:    Re: workaround for glibc bug
From:       Leo Savernik <l.savernik () aon ! at>
Date:       2007-09-28 17:40:05
Message-ID: 200709281940.06429.l.savernik () aon ! at
[Download RAW message or body]

Am Donnerstag, 27. September 2007 schrieb Matthias Kretz:
> Clarification on the issue:
> it's not easy to hit the deadlock:
> a) you need an application that uses threads
> b) that application needs to be resolving symbols in both threads at the
> same time
>
> Now, this issue is hit with xine-lib a lot more easily than with your
> average KDE application. I'd say you get a deadlock every 100th-400th time.
> (If my felt statistics ;-) are correct then every KDE4 user will see the
> deadlock from time to time.)
>
> So what does it mean for you? If you are using Phonon a lot either "export
> LD_BIND_NOW=1" or update to glibc-2.6.90-14 or higher (I won't update until
> my distribution provides the update). Otherwise ignore the issue.
>
> Freeze means that only this one app will freeze. Depending on what app that
> is it's more or less critical. And often it's also not the main-thread that
> deadlocks - e.g. the GUI still works but the audio playback has stopped.

Can you work around it by using the null backend? (Assuming switching to 
another functional backend wouldn't change the situation.)

mfg
	Leo

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