summaryrefslogtreecommitdiff
path: root/source3/script/gen-8bit-gap.sh.in
diff options
context:
space:
mode:
authorVolker Lendecke <vlendec@samba.org>2004-06-20 08:37:01 +0000
committerGerald (Jerry) Carter <jerry@samba.org>2007-10-10 10:51:59 -0500
commit5db731d899987d1a53e72f16b92b7e01eafd80c2 (patch)
treea4f1cb1d1caa48ddb26120131b9a16abbab0f346 /source3/script/gen-8bit-gap.sh.in
parentee79226d2a4486be66b47e7ff86e40f91c654ba7 (diff)
downloadsamba-5db731d899987d1a53e72f16b92b7e01eafd80c2.tar.gz
samba-5db731d899987d1a53e72f16b92b7e01eafd80c2.tar.bz2
samba-5db731d899987d1a53e72f16b92b7e01eafd80c2.zip
r1202: This hopefully fixes our memory use when unmarshalling strings. The test case
was 'rpcclient -c "enumprinters 2"' with 4000 printers. At some point this completely exploded in memory usage. For every string we talloc'ed memory up to the end of the buffer. -> O(n^2). This survives valgrind with this number of printers. It might also have influence on winbind with a large number of users. All those who dare to look at samba3 rpc code, could you please take a look? I know this is a burden, but I would like comments ;-))) Volker (This used to be commit af251f4ea63c584604972e1c8add83e65046de80)
Diffstat (limited to 'source3/script/gen-8bit-gap.sh.in')
0 files changed, 0 insertions, 0 deletions