There's an issue with apexcontrol going out of scope. There's an incorrect free happening in relation to bufferedprocessing. It happens only occasionally.
My guess is that the thread responsible for filling the buffer is freed after the buffer itself. It could only happens rarely because the thread that fills the buffer is a different one from the thread that calls delete.
There's an issue with apexcontrol going out of scope. There's an incorrect free happening in relation to bufferedprocessing. It happens only occasionally.
My guess is that the thread responsible for filling the buffer is freed after the buffer itself. It could only happens rarely because the thread that fills the buffer is a different one from the thread that calls delete.