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

List:       kde-core-devel
Subject:    Re: Review Request: Workaround for non-thread-safety of
From:       Sune Vuorela <nospam () vuorela ! dk>
Date:       2010-05-28 9:27:15
Message-ID: slrnhvv33j.rvp.nospam () sshway ! ssh ! pusling ! com
[Download RAW message or body]

On 2010-05-27, Thiago Macieira <thiago@kde.org> wrote:
> It's not theoretical. It's quite easy to run into that issue: if the mutex > is 
> unlocked for a callback, the other thread will not be able to send the 
> message. It will fail.

I guess it is the same issue I'm seeing with nepomuk* filling
.xsession-errors with "OUT OF MEM" lines at a rate of several hundred
megabytes pr hour.

/Sune

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