Editing Lepiter pages slows to a crawl after committing to the repo from an associated git view

[onierstrasz]

After committing changes to a repo from a git view associated to a lepiter page of that project, it becomes almost impossible to type into Lepiter pages of a database belonging to that repo.

Steps to reproduce the problem

• Load a repo with both classes and a lepiter database
• Open a page of that project containing a code snippet that uses a class of the project
• Modify the page or the class so there is a change to commit
• From the code snippet, open the code bubble of the class and click on the Go to repository button
• Commit and push the change
• Try to type into a text or code snippet of the lepiter page and you will experience a massive slowdown.

You can close the git view and the page and all other open pages, but if you go back to the same page, or any other page of that repo's database, and try to type, it will still be slow.
Typing in pages of other databases is fine.
If you perform Smalltalk garbageCollect, the problem will be fixed.

Curiously, if you commit changes directly from the Git tool rather than navigating from the page to the git view, the problem does not arise. Also, maximizing the git view to see the full tool before committing appears to avoid the problem.