Changes between Initial Version and Version 1 of Ticket #13519, comment 13
- Timestamp:
- Nov 27, 2019, 11:58:10 PM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #13519, comment 13
initial v1 5 5 > Looking carefully at the valgrind messages following line 10876 it shows that the "invalid read" is done by the signal monitor; it is reading the value just free'd by the scanner. 6 6 7 I have this recollection this (or something like it) was reported in a previous ticket, and SiliconDust indicated that you needed to create a new object for each thread... 7 I have this recollection this (or something like it) was reported in a previous ticket(*), and SiliconDust indicated that you needed to create a new object for each thread... 8 9 10 (*) Yes, found it! #9027 which was closed WONTFIX at the time. Note I have not actually spent time to determine if this is *actually* the same issue, so this might be an untamed fowl chase, but the symptoms, in the same library, certainly raise an eyebrow.