Skip to content

World age assertion in codegen #29267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Keno opened this issue Sep 19, 2018 · 6 comments
Closed

World age assertion in codegen #29267

Keno opened this issue Sep 19, 2018 · 6 comments

Comments

@Keno
Copy link
Member

Keno commented Sep 19, 2018

After pulling master today, my current project is giving the following assertion error:

Assertion `li->min_world <= world && li->max_world >= world' failed.

Cursory debugging suggests the method has been deleted in the current world. Investigating further.

(rr) p li->min_world
$9 = 25116
(rr) p world
$11 = 28906
(rr) p li->max_world
$14 = 28839
@Keno
Copy link
Member Author

Keno commented Sep 19, 2018

Looks like this is happening while compiling

load_proto(TensorFlow.tensorflow.AttrValue) [ World Bounds 28897:∞ ]
_isfilled(TensorFlow.tensorflow.AttrValue_ListValue, Symbol, Bool) [ The li from above ]

which are part of TensorFlow.jl/ProtoBuf.jl. This is odd, because the _filled method was deleted before the load_proto was created so it shouldn't have been able to see it.

@Keno
Copy link
Member Author

Keno commented Sep 19, 2018

I just rebuilt julia and this went away. I do still have the rr trace if we want to do some debugging, but this is fairly mysterious. Maybe @vtjnash has an idea where to look.

@timholy
Copy link
Member

timholy commented Sep 19, 2018

Were you using Revise? If so, and if you hadn't updated packages in a while, it could have been timholy/Revise.jl#191.

@Keno
Copy link
Member Author

Keno commented Sep 19, 2018

Revise was loaded, but the method in question was not deleted by Revise. Rather it got invalidated when another package was loaded.

@Keno
Copy link
Member Author

Keno commented Sep 21, 2018

I still see this intermittently every time I rebuild julia. Just rebuilding again makes it go away, but it's definitely not fixed. I also did upgrade to mater of Revise in the meantime, just in case (but the error's still there).

@vtjnash
Copy link
Member

vtjnash commented Aug 2, 2019

This is pretty old now, so I'm going to presume it fixed by #31191 and see if any new issues get opened as they pop up.

@vtjnash vtjnash closed this as completed Aug 2, 2019
phyatt-corp added a commit to Conning/julia that referenced this issue Dec 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants