Extending NewDefaultUrlProvider leads to error

[karlmacklin]

@lawejo I saw your thread here:

Publishing performance issue in Umbraco 17 when using a custom IUrlProvider / NewDefaultUrlProvider

Hi everyone, I’m hoping someone can help me understand a performance issue I’ve run into after upgrading a project from Umbraco 13 to Umbraco 17. In Umbraco 13, I had a custom URL provider inheriting from DefaultUrlProvider. In that version, GetUrl() was only executed when the URL for a specific node was required, and publishing a parent node did not cause URL lookups for all of its descendants. In Umbraco 17, I have tried both implementing IUrlProvider directly and inheriting from NewDefault…

Did you run into any similar issue when extending NewDefaultUrlProvider?
And did you find any solution to the caching issue?