-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
many false positive invalid heap args on 64-bit Chromium tests #1839
Comments
In fact we are also seeing false positives on smaller apps on some platforms: Win8.1 on hello64:
Win10 on 64-bit notepad where I opened the Save As dialog: Hit several invalid heap args, due to callstack not matching auto-suppress?
+2 more |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The 64-bit FYI test bot is now up and running, but there are many reported invalid heap args.
Xref #1831. These may similarly all be due to bad callstacks: xref #1222, #1833.
http://build.chromium.org/p/chromium.fyi/builders/Windows%20Tests%20%28DrMemory%20x64%29/builds/18
media:
ipc:
There are many instances of invalid heap args involving RtlProcessFlsData:
ipc not visible in bot stdio, also base:
Same thing in this particular test for net_:
Plus a bunch of other tests:
Also in components, device, cloud_print, mojo_system, cast, extensions,
google_apis, and unit_.
Different bogus callstack in net_:
Seems like MSVCR100D!_freefls should be on the callstack.
Xref #1278; xref #997 _getptd. Probably this is similar, with some
internal libc routine being called on alloc resulting in our first
interception being at the WinAPI layer.
Sure looks like a bogus callstack frame -- and maybe it becomes a
"potential error" w/ proper callstack?
In content_, missing some frames so doesn't match #960 suppression (xref #1831):
I can't repro any of these invalid heap args locally!
They may well only occur with a lack of libc symbols, so this is my template for attempting to reproduce:
I tried media and ipc individual and running full suite from bot, both w/ my build and w/ DrMem unpacked/.
Maybe it's best to just disable this feature on the bots? We already do this for Windows Release:
So we'd add -no_check_heap_mismatch.
Xref #1838: add new option -malloc_callstacks to obtain malloc info for mismatch errors in light mode, and turn on for chrome?
The text was updated successfully, but these errors were encountered: