>> This is why it seemed quite odd or like things where leaking, also because >> 1600x1200x4Bytes for RGBA = about 7Mb and I've got 512Mb ram on the GPU >> side of things, >See these bug reports >https://bugs.kde.org/show_bug.cgi?id=261069 >https://bugs.kde.org/show_bug.cgi?id=260248 > >esp. the 260 series seems to cause /real/ trouble (on some GPUs - works fine >here so far), maybe try to downgrade (if this didn't happen before) > >Also consider testing whether the XRender backend shows better performance.
I actually upgraded to the 260 version of the drivers to see if that corrected the issue, I've tried a few different versions and I'll give the open-source ones a go too. I'll give XRender another shot too. > Ps: > you tend to drop from one issue to the next, what makes your mails... > "long", > try to separate your issues and report them to the proper destination, ie. > a) using the bugtracker > b) assigning to the affected "product" > > this will get you more informed reply and maybe deeper insight into the > problem through the reports of others. > Ok, the problem was possibly that I listed lots of 'facts' without actually seeming to get to the point.You could say I express the context I am thinking off by saying the things that represent the context and not actually the context it's self. But that's as I don't know the options or the 'best' way to go about it and I think 'black' and 'white' so anything in-between could either be possible or not possible, a chance in a billion is still a chance. So there are to many 'possibilities' without me being able to narrow down things a little. This is similar to the problem I have with reading, too many possible interpretations. Also coming off and being on the mind-control pills was causing havoc. The points was that I was quite interested into getting into doing more work on KDE again, the two issues I had where really more of a way wanting to get more in-site into how to do things, since it's been a number of years since I touched KDE etc.. There where some other things, which I dropped from the email because it was apparent it was starting to ramble on a bit. I do use the bugtracker quite a bit, especially if there's a clear crash or something to report. When I've used it in the past (many moons ago) it's taken time to get anywhere in particular, but as I'm willing and able to put some of that work and effort in, or even fix it myself. I fealt that may be a better approach. Again. I'll look at the bugs reports. > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to > unsubscribe << >
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
