Nuitka 2.0 stuck when build vedo, seem go into an infinite loop about nuitka HOT 6 CLOSED

Thanks for your report, this is fixed on the factory branch, which is a development version under rapid development. You can try it out by going here: https://nuitka.net/doc/factory.html

Feedback if this is working is very welcome, just please do not share plans of doing it, but rather confirmations or denials of it working.

from nuitka.

With stuck you mean, like no output anymore, that's indeed very not good.

from nuitka.

It's reproducible if I attempt to only compile the vedo.addons backing file with --module. It seems stuck on this line:

acts = titles + lines + labels + grids + framelines

And apparently it's endless looping trying to get the type shape of lines which is not a particularly hard variable. It's assigned from [] and then appended a few times, but then seems to get stuck in that lookup.

from nuitka.

This code was added at some point:

                if trace1.isEscapeTrace() and trace1.previous is trace2:
                    version = versions[0]
                elif trace2 is trace1.isEscapeTrace() and trace2.previous is trace1:
                    version = versions[1]
                else:
                    version = self.addVariableMergeMultipleTrace(
                        variable=variable,
                        traces=(
                            trace1,
                            trace2,
                        ),
                    )

The intention was to avoid merge traces of traces that may or may not be escaped, and replace them with the escaped trace only. However, the second branch has a typo trace2 is that made it ineffective in those cases. Recent changes make escape traces actually consider their previous trace, before it was essentially giving unknown type shape. At that point, this became way more than a waste of memory, it became a scalability issue, where the ever deeper nesting of those traces could render code to become slower and slower to optimize the more escapes (usually unknown code can run) are seen.

The result of this will be two fold. Some codes will use a lot less value traces now, which would always have been a good idea, and this now compiles in somewhat acceptable time, albeit not too fast.

from nuitka.

Thanks for your report, this is fixed on the factory branch, which is a development version under rapid development. You can try it out by going here: https://nuitka.net/doc/factory.html

Feedback if this is working is very welcome, just please do not share plans of doing it, but rather confirmations or denials of it working.

Thanks for your comment, factory branch works for me.

from nuitka.

This is part of the hotfix release 2.0.1 that I just made.

from nuitka.