Hi @JenniferCadkin
In the 3.5.5 release notes I did not see anything around performance fixes or addressing the slow-down 3.5.x experiences over time as an instance is kept open.
Is this something you might know they looked at for 3.5.5?
Unsure if this is what Mark is seeing - in a long editing session things like moves and vertex editing, tracing a new feature along another with dense vertices, etc exacerbated the slowdown issue and I am now in a habit of restarting Pro every hour or so (avoids this issue and reduces likelihood of encountering the freeze on copy issue).
My experience with 3.5.4 shows that @Mark_Eygenhuysen is unlikely to see an improvement in behaviour going to 3.5.4
@Mark_Eygenhuysen As you are stuck with 3.5.0 as long as your client is on it, make sure to avoid BUG-000176644 related to SQL expression based filters and selections in FGDB data. It can mess up your day if you run a calculation and it updates the entire dataset instead of just the selection you thought you had.
