Remove assertion from ~LockedPageManager

[crowning-]

References:

• https://dashtalk.org/threads/v12-testing-thread.5484/page-48#post-58668
• V0.12.0.x fix ds mn crashes #395

Bitcoin solution:

• Remove assertion from ~LockedPageManager bitcoin/bitcoin#6144

[UdjinM6]

I would prefer git cherry-pick 881027a to have a nice history instead of creating yet another commit from scratch :)
smth like that UdjinM6@05b31b7

[crowning-]

Didn't know the cherry-pick option...I'll try that.

Edit: Hmh, obviously I'm missing something: "fatal: bad revision '881027a'"

[UdjinM6]

@crowning- add bitcoin as a remote, fetch it and then cherry-pick

[crowning-]

I already tried that:

git remote add upstream https://github.com/bitcoin/bitcoin.git
fatal: remote upstream already exists.

No, I've never added it before...
Anyway, a direct

git fetch https://github.com/bitcoin/bitcoin.git

did the job.

The commit looks a bit odd now because no file was changed, but I guess we can live with that.

[UdjinM6]

errr... I thought of replacing you commit with cherry-pick, not adding it to yours actually
smth like this (using stash is optional - it should save your current work if you have smth uncommitted):

git stash
git reset --hard HEAD^
git cherry-pick 881027a
git push crowning- HEAD -f
git stash apply

since now you now have 2 commits already:
git reset --hard HEAD^ should actually be done twice or replaced with git reset --hard HEAD~2