Repeater crashed VS
-
I try to repeat a pattern but VS always crashed: VS is not responding & I have to force quit the app but no crash report.
-
@Pat On Windows the force quit cannot create crash logs.
I will try to replicate this issue.
Is there an example that if repeated results in a crash?
-
@VectorStyler VS is not responding as soon as I click on the '+' to make the repeated pattern.
-
@Pat Is that object a clone?
-
@VectorStyler Yes, it is.
-
@VectorStyler I wanted to duplicate the iobject to test further but I got this (AltClick-drag):
-
@Pat Looks like there are more issues with clones. These are bugs.
-
@VectorStyler I've sent you one file
-
@Pat Got it!
-
@VectorStyler I can duplicate the blended & cloned objects if I expand first into a group of objects:
-
@Pat What happens if first the blended objects are grouped and then duplicated?
-
@VectorStyler I've just reopened one 1.1.079 file with a "repeated" object and it is wrong:
-
@VectorStyler the blended objects were already grouped & it can not be duplicated without expanding...
... but repeater does not work even with expanded objects.
-
@VectorStyler Sorry to say but I have tried the "Repeater" feature with a new document but nothing works. The object contained about 20 lines and it crashed VS (no response, the fans started to run at maximum... impossible to launch the W11 manager) and I ended up having to force VS to close. I don't recall having such extreme issues before version 1.1.08.
-
@Pat What is the size of the repeater grid in these cases? I also tested with the file sent earlier (and the cloning issues were found, but not yet fixed) and I think one problem is that the repeater is just too large.
-
@Pat BTW: these repeater issues (with the cloning) can be replicated and will be fixed soon.
-
@Pat Replicated this latest crash (freeze) also. Somehow there were 1.2 million repeated objects
, will fix this ASAP.
-
@VectorStyler It was not so large (did draw within the artboard) but I should have setup the Repeater feature before applying... did not think about it, though I didn't have these issues with 1.1.079.
