Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

mikem8361
Copy link
Contributor

Need to check s_callCountingManagers is not null in the CallCountingManager enumerate memory function.

@mikem8361 mikem8361 added this to the 5.0 milestone Feb 1, 2020
@mikem8361 mikem8361 requested a review from kouvel February 1, 2020 02:48
@mikem8361 mikem8361 self-assigned this Feb 1, 2020
@mikem8361 mikem8361 requested a review from noahfalk February 1, 2020 02:48
@jkotas
Copy link
Member

jkotas commented Feb 1, 2020

The PR that introduced this problem was reverted in #30105. I have added note to #29934 to include this fix in next attempt.

cc @kouvel

@jkotas jkotas closed this Feb 1, 2020
@mikem8361 mikem8361 deleted the fixcreatedump branch February 13, 2020 01:31
kouvel added a commit that referenced this pull request Mar 3, 2020
* Improve call counting mechanism

- Commit 1
  - Reverts commit f954c6b, which reverted PR #1457 due to issues
- Commit 2
  - Fixes crashes and assertion failures seen by the original change, fixes #29934
  - The crashes were caused by commit 6aa3c70 in the original PR
  - Call counting infos cannot be deleted when the corresponding call counting stubs may still run, because:
    - The remaining call count decremented by the stub is in the call counting info
    - The only way to get a code version / method desc from a stub is to go through the call counting info
  - Got one repro of the assertion failure in #22786 and it is most likely caused by the same issue, following heap corruption from modifying a deleted call counting info where the memory is reused for a `NativeCodeVersionNode`, messing up the method desc pointer
  - Fixed with a partial revert of the above commit. Added back the `Complete` stage and then call counting infos are deleted only after it's ensured that call counting stubs won't be used (shortly before deleting them).
- Commit 3
  - Public static functions of `CallCountingManager` that may be called through the debugger may occur before static initialization, added a check for null as suggested in #29892

* Fix crashes and assertion failures seen by the original change

* Add check for null for some functions callable from the debugger
@ghost ghost locked as resolved and limited conversation to collaborators Dec 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants