It seems the breadcrumb attempts to render the text field of the parent tiddlers to use as path segments, provided that the field is not blank; otherwise the title field is used instead.
If lazy-loading of image tiddlers is enabled, the breadcrumb will initially see a blank text field before the first time an image-typed tiddler is opened, so the breadcrumb renders the title fields instead; everything works.
As soon as the image-typed tiddler is loaded, the text field becomes populated with the encoded string representation of the image. In the case where the image is very large, some of tiddlywiki's functions (split[], I guess?) can break trying to parse the long string.
A simple fix is to omit image-typed and binary-typed tiddlers when generating the breadcrumb. In $:/plugins/sq/streams/breadcrumbs-view-template:17, instead of:
textfield of the parent tiddlers to use as path segments, provided that the field is not blank; otherwise thetitlefield is used instead.textfield before the first time an image-typed tiddler is opened, so the breadcrumb renders thetitlefields instead; everything works.textfield becomes populated with the encoded string representation of the image. In the case where the image is very large, some of tiddlywiki's functions (split[], I guess?) can break trying to parse the long string.A simple fix is to omit image-typed and binary-typed tiddlers when generating the breadcrumb. In
$:/plugins/sq/streams/breadcrumbs-view-template:17, instead of:one can change it to:
which resolved the issue for me.