[cups.bugs] [LOW] STR #1660: Large stack buffers worry libMallocDebug.dylib

[jlovell.apple]

[STR New]

This is: <rdar://4535214> cups stuff makes libMallocDebug log lots of
warnings.

This is caused by stack frames larger than 64KB -- e.g. functions with 64K
stack based buffers.

Application developers who use libMallocDebug.dylib (and hopefully many
do) will see this when doing any print activities.

To reproduce:
$ export DYLD_INSERT_LIBRARIES=/usr/lib/libMallocDebug.A.dylib
$ lpq
libMallocDebug[23877]: initializing libMallocDebug on thread d03
libMallocDebug[lpq-23877]: frame pointer goes from bffef150 to bffff230 --
assuming invalid.
.... repeated 500+ time...
libMallocDebug[lpq-23877]: frame pointer goes from bffef150 to bffff230 --
assuming invalid.
HL_5250DN_series is ready
libMallocDebug[lpq-23877]: frame pointer goes from bffeec00 to bfffece0 --
assuming invalid.
libMallocDebug[lpq-23877]: frame pointer goes from bffeec00 to bfffece0 --
assuming invalid.
libMallocDebug[lpq-23877]: frame pointer goes from bffeec00 to bfffece0 --
assuming invalid.
libMallocDebug[lpq-23877]: frame pointer goes from bffeec00 to bfffece0 --
assuming invalid.
no entries

The 64K buffers are rather large... halving them won't reduce performance
(and may actually help due to better usage of the kernel's disk read-ahead
buffers).

Comments?

Thanks!

Link: http://www.cups.org/str.php?L1660
Version: 1.2-current
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: small-buf.diff
URL: <https://lists.cups.org/pipermail/cups/attachments/20060505/0811808b/attachment.ksh>