site_archiver@lists.apple.com Delivered-To: bluetooth-dev@lists.apple.com To follow up on this: Joe K. On Oct 29, 2007, at 3:57 PM, Joseph Kelly wrote: Is there any known issues with RFCOMM running on Leopard? This was working on 10.4.10. If not, I'll file a bug. Joe K. _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/joeman%40mac.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.a... This was my own mistake: I found that I was passing a raw CFData byte pointer (obtained from a message port callback) to the main thread without first retaining it. The message port callback would return, free the data, and in the main thread I would then RFCOMM-write the now invalid data. Apparently Leopard has instituted some new policy whereby the OS reclaims and re-uses freed memory ;-) I can write data to my company's device, but every once in a while, I stop receiving expected data. This email sent to joeman@mac.com This email sent to site_archiver@lists.apple.com