James Bucanek wrote:Very interesting. What's curious is that those messages are from the debug version of the malloc libraries, and as far as I know I didn't ship any versions of QRecall that use the debug malloc library. It might be possible that you have an environment variable set that enables this (this might even be standard on the server). It's worth investigating.
I wouldn't have the slightest idea how to investigate that, much less even set the environmental variable. I did, however, install the Xcode tools on the server. Might that have done something?
Regardless, the messages appear to be coming from the QRecall client. Since you suspect that this occurred in the last 48 hours, do you happen to remember what you might have been doing in the QRecall application lately? This would help me in trying to reproduce the problem.
In that period of time, it ran some actions that were created by the assistant. I modified them all to change from "hold" to "ignore" if the backup drive was not present. I changed the interval on the capture from once a day to once an hour, for a few hours, then back to once a day again. I probably opened the archive a few times to check that everything was working. And that's all I can think of.
I'm going to the server now to see if I can duplicate it. I'll report back shortly...
-- Bruce