On 2/17/23 12:07, Jason McKesson via Std-Proposals wrote:
> You realize that this proves precisely nothing, right? The source of
> the bug could still be in your code. Switching memory allocators means
> switching where the heap tracking stuff is (and a GPU allocator
> probably puts heap tracking in your CPU's memory rather than GPU
> memory of which there is far less). So a wild-write which on one
> allocator hits heap tracking data, would very likely miss heap
> tracking data on a different allocator. It would hit something else,
> something that your program is able to tolerate better.

I admit I'm using OpenCV4, and I did find some non-atomic reference
count issues in their code but I did fix them.

So anyway I'll write down a simple application whenever I find a copy of
Windows at home and I'll compile statistics to prove my point.


Thanks,

-- 
Logo <https://www.fornux.com/>  
*Phil Bouchard*  facebook icon
<https://www.linkedin.com/in/phil-bouchard-5723a910/> 
CTO
T: (819) 328-4743
E: phil_at_[hidden]| www.fornux.com <http://www.fornux.com>
8 rue de la Baie| Gatineau (Qc), J8T 3H3 Canada
Banner <https://goglobalawards.org/> Le message ci-dessus, ainsi que les
documents l'accompagnant, sont destinés uniquement aux personnes
identifiées et peuvent contenir des informations privilégiées,
confidentielles ou ne pouvant être divulguées. Si vous avez reçu ce
message par erreur, veuillez le détruire.
This communication (and/or the attachments) is intended for named
recipients only and may contain privileged or confidential information
which is not to be disclosed. If you received this communication by
mistake please destroy all copies.