Just tried to look for the '80 Byte' leak per PanedW creation/deletions
I can see for test/Xm/panedw/test9
It turned out that there is no simple '80 Byte' leak, but there
is a more complex dependency ...
At least on one machine (this is all on alpha/linux/gcc) I got not even
the curve one might expect:
leak(number) = constant_class + constant_widget * number
where constant_class is some number which is independent of the
number of calls. It turned out that I roughly get this curve but
- the leak does not exist for n <= 17
no explanation ...
- somewhere near n=130 I got another maximum
even harder to explain than the previous result ...
Optimization level for libXm and test9 was supposed to be -O1,
perhaps I should try again with -O0.
--
Alexander Mai
[EMAIL PROTECTED]
