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

List:       kde-devel
Subject:    Re: Followup: Howto reduce X11 memory usage with several QCanvas /
From:       Achim Spangler <Achim.Spangler () mnet-online ! de>
Date:       2004-06-28 12:19:59
Message-ID: 200406281419.59372.Achim.Spangler () mnet-online ! de
[Download RAW message or body]

Am Sonntag 27 Juni 2004 19:19 schrieb Maks Orlovich:
> Achim Spangler wrote:
> > Just a small data update based on the information from xrestop:
> >
> > res-base Wins  GCs Fnts Pxms Misc   Pxm mem  Other   Total   PID
> > Identifier
> > 3400000   728  117    5  535  384   562172K     33K 562206K   ?
> > MiniVegN.xmi
> > [GeĆ?ndert] - Umbrello UML-Modeller
> >
> > --> xrestop reports 562MB "Pxm mem"
>
> http://lists.kde.org/?l=kde-core-devel&m=107298440324722&w=2 has a pair of
> patches (one to Qt, one to kdelibs) that can help trace what the allocated
> pixmaps are... Alternatively, if the XMI file in question is publically
> available, or some other one that shows the problem is, I may be able to
> help out..
As far as I understand the SVG export possibility of Qt ( QtPicture ), I 
should be able to achieve a comparable result by creation of a SVG export - 
trigger paint into the paint device QPicture - and then call SVG export of 
QPicture.

Or could it happen, that some double allocated items are exported only once by 
QtPicture?

In case the SVG export can be also used to analyse the correct diagram 
display, the painting algorithms seem to be correct.

Bye,
Achim
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

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