SP Crashing

[Cantor, Scott]

On 9/19/19, 5:38 PM, "Dan McLaughlin" <dmclaughlin at tech-consortium.com> wrote:

> I have the debug symbols loaded and SP source downloaded with Windbg
> installed.

The result is pretty indistinguishable to me from not having them, so I'd have to take your word for it, I don't actually know what that would look like. The heap corruption does suggest a real bug and not just memory allocation problems, but the only bugs that can usually be tracked down are the ones that are reproducible with specific transactions.

> Is there any logging I could enable that might help point me in the right direction?

As I said, there's DEBUG and there's nothing, and DEBUG itself is pretty much nothing with this sort of thing unless it's reproducible under specific circumstances with a single transaction, otherwise it's just noise. Race conditions don't manifest anywhere near the actual code causing them.

INFO alone would log metadata or configuration reload events, and if there are any in proximity to the crashes every time that might be suggestive.

If you're using any newer V3 features, I'd avoid them and if that makes a difference then that's a solid direction for research, but nothing that's going to result in a fast answer.

If there really is a race condition (and since it's not crashing for lots of other people across thousands of installs, it seems plausible that it's load-based), then spreading the load is obviously the most likely thing that will reduce the frequency.

-- Scott