It sounds that perhaps there is an event listener where you are inadvertently changing the property again.
Perhaps try setting a breakpoint in the setter of the generated code, as suggested by this answer https://stackoverflow.com/a/9005656/141022 to try and spot the loop.
And turning of step over properties in the visual studio debugger settings.
And perhaps removing the DebuggerStepThrough from the generated code temporarily (if it's there) to see if you can step into the property.
The linked answer (although not directly related) may give you some hints.
Perhaps the callstack might give you some hints as well, but I'm guessing it could be tricky to read if it's across threads.