Bug 408364 - Valgrind causes OOM when running a function in a deleted virtual class
Summary: Valgrind causes OOM when running a function in a deleted virtual class
Status: RESOLVED NOT A BUG
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (show other bugs)
Version: 3.15 SVN
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-06 00:37 UTC by krzysio.kurek
Modified: 2019-06-09 17:54 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Source code to replicate the issue (150 bytes, text/x-c++src)
2019-06-06 00:37 UTC, krzysio.kurek 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description krzysio.kurek 2019-06-06 00:37:24 UTC 
Created attachment 120611 [details]
Source code to replicate the issue

SUMMARY
If you try to run a virtual function on a deleted object, valgrind starts allocating massive amounts of memory before running into a system-wide OOM

STEPS TO REPRODUCE
1. Compile the attached code
2. Run under valgrind

OBSERVED RESULT
Code is ran, an error is optionally reported and valgrind exits

EXPECTED RESULT
Valgrind starts allocating massive amounts of memory, never exits.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Linux-5.1.5-1-default OpenSUSE Tumbleweed
Comment 1 krzysio.kurek 2019-06-09 17:54:03 UTC 
Turns out it was caused by thread sanitizer which I forgot was on.