Inkscape freezes after selecting an object which has linked clones

On OS X 10.7.5:
- not reproduced with Inkscape 0.48.5
- reproduced with 0.91 r13725 and 0.91+devel r14194

Requirements to reproduce the reported performance issue:
- 'Fill and Stroke' dialog has been opened in the current session
- Marker options use default settings:
  [x] Color stock markers the same color as object
  [ ] Color custom markers the same color as object
  [x] Update marker color when object color changes

AFAICT the issue does no longer reproduce after unchecking one of the two by default enabled marker options in the preferences (it doesn't matter which one).

Further reduced test case: only one marker, only one clone (no nested clones (clone of clone of clone of ...)).

I can also reproduce this bug with 0.92.2 on Fedora 26 and both, 0.92.1 and 0.92.2 on Windows 7 with different builds. Please note that it can not always be reproduced. The CPU runs into a busy loop in most cases, which sometimes leaves the application intact and sometimes locks it up to be unresponsive. If the application is not being blocked, the edit history breaks, showing many items which were never executed. This issue looks like a use-after-free bug which should be easy to track down using valgrind.

inkscape is very hard to run under valgrind due to its use of libgc. Are there any known steps how to debug inkscape under valgrind?

I can still reproduce the bug with Fedora's inkscape-0.92.3-2.fc28.

I can try compiling Inkscape from current source code and reproducing there if it helps.

Attaching a different example (seems group might make it even worse). Enter the group of the left two paths, click on the one with arrow -- and the GUI gets stuck.