I don't remember the previous discussion. When you tell fuel to serialize an object, it traverses the references of that object *to* other objects. By default, it uses some criteria to prune the traversal. For example, when the traversed object is a class, then it encodes the name of that class. Similar for a method.�

So I think in some way your object is referencing that problematic block closure.�

Maybe it can give you a clue if you put a halt in FLAnalysis>>trace:�

Maybe a "self haltIf: anObject�isClosure"

HTH,

Mart�n

On Mon, Oct 28, 2013 at 8:16 AM, roberto.minelli@usi.ch <roberto.minelli@usi.ch> wrote:

Hi,

I�m struggling with Fuel and I probably discovered my problem.

When trying to serialize an object (that represents a development session, i.e., contains some meta-data (title, author, etc.) and some objects representing actions of the developer) I often encounter problem with some BlockClosure�s which are somewhat corrupt and Fuel crashes and cannot serialize them. We already discussed this issue in this mailing list a while ago with Max.

I do not ask directly Fuel to serialize some BlockClosures, so my intuition is that Fuel serializes all the references to the objects I am trying to serialize. Am I right? Is there any way to tell Fuel not to do so?

Cheers and thanks for the help,
Roberto