F
Fernando Souza
Guest
Yes, this can be reproduced in 11.3.2 too. But we have recently fixed a bug that has to do with garbage collection happening too soon on a chained reference and the crash cannot be reproduced anymore (this issue will be fixed in the next 11.3 service pack). As a workaround, break up the statement so that either: - the object being new'ed during the chained call is assigned to a variable. - the method call getFolder() is not executed in the same statement. For example, the statement before the message statement in temp.bar:foo() could be changed to : dir1 = temp.io:directory. dir1:create(substitute("&1/.backup",getFolder())). or var1 = getFolder(). temp.io:directory.create(substitute("&1/.backup",var1)).
Continue reading...
Continue reading...