[SOLVED] Removing unreachable <Some Object>... on game exit

[RangerDanger]

While testing some portions of a game I am working on, one of our team members noticed a "odd" line in the console when config.debug is set:

Code: Select all

Removing unreachable: <renpy.python.RevertableObject object at [...]>

Where [...] is some memory address.

I was curious as to what exactly this means and if this is something that we should be worried about. We have not noticed any adverse effects that seem to be linked to this at all in our testing.

[PyTom]

This isn't a problem - it's just some debug output from the save/load system. You can safely ignore it.

It's a print that happens if you do:

Code: Select all

init python:
    class MyObject(object):
         pass

python:
     a = MyObject()
     a.foo = 1
     a = None

That is, an object gets a change that puts it into the rollback log, but never actually becomes reachable from a savegame.

In general, config.debug is more for my use than yours - I might ask someone to turn it on if a weird error occurs, to prevent the error from being suppressed. config.developer turns on checking that I think would benefit developers.

[RangerDanger]

This isn't a problem - it's just some debug output from the save/load system. You can safely ignore it.

It's a print that happens if you do:

Code: Select all

init python:
    class MyObject(object):
         pass

python:
     a = MyObject()
     a.foo = 1
     a = None

That is, an object gets a change that puts it into the rollback log, but never actually becomes reachable from a savegame.

In general, config.debug is more for my use than yours - I might ask someone to turn it on if a weird error occurs, to prevent the error from being suppressed. config.developer turns on checking that I think would benefit developers.

Thanks for clearing that up.

We were altering some Ren'Py behavior to fit our needs better, so I figured it might be beneficial to have on. Good to know it isn't something that requires attention