Dart Compiler fail about sdk

[fishythefish]

-137438953473 is 0b1111111111111111111111111101111111111111111111111111111111111111. That's a bit flip from -1, which is how TreeNode.noOffset is encoded. If you try a fresh build and this problem doesn't reoccur, it might have just been a memory error that got persisted.

[biggs0125]

Hi, sorry you've run into this issue.

Would you be able to provide a bit more context on the app you're running and your build environment? For example, are you passing any additional flags to the Dart web compiler?

Also this isn't always possible but if you could share the code for the app you're running or a snippet that demonstrates this behavior, that would be great. Thanks!

[normcf]

command line:
nice dart run build_runner build --define "build_web_compilers|entrypoint=compiler=dart2js" -o web:build

[normcf]

Nate, Thanks for your response. I cannot share the code, but I will be happy to share a screen and let you play with it (if you help me to do that as I have not done that in a very long time). My number is 703 991 9383 (John). I am in Virginia (EST). Maybe text first, if you can, as I usually do not answer numbers I do not recognize and I have some meetings blocking my time too. The application is quite large now. When I tgz the whole compiled thing (which includes dart, php and help docs with jpegs) it comes to ~200M. The part I install (the build directory) is smaller. It is probably not built like most applications in that there are many pages with a main, There are also some base libraries that are shared across all the pages. The application requires a database and php to run, but you probably don't care about that. The failure was on one of those mains, but the first time it failed it ran through many mains before getting to the one that failed. It now fails on that main immediately as it must know that the other mains were successful. I don't believe I made any changes in the code specific to that main, but it could be including something I changed. I just checked and that dart file has not changed since September and I have done many builds since them. I have not tried wiping out the build area to restart from the beginning. Also, some Ubuntu patches for applications have come, but I have not restarted to make all those changes effective. I can try those things if you think it is worth a try. Do you want the yaml file added to the problem report?

…

On Wed, Feb 21, 2024 at 1:27 PM Nate Biggs ***@***.***> wrote: Hi, sorry you've run into this issue. Would you be able to provide a bit more context on the app you're running and your build environment? For example, are you passing any additional flags to the Dart web compiler? Also this isn't always possible but if you could share the code for the app you're running or a snippet that demonstrates this behavior, that would be great. Thanks! — Reply to this email directly, view it on GitHub <#54966 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXTVKQ6OEZHPDEOZKWHNWTYUY4BVAVCNFSM6AAAAABDR2674OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJXGYZTMNBXGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- John Yendt

[normcf]

I did some work, which required to go back to the dev compiler. I did not change any dart code. I made some back end php changes. Finally, I started a dart compile and this time it succeeded. It may have just been luck in some compile order, but it finished successfully. Do you want to keep this open? Or should we close and start a new issue if it recurs?

[fishythefish]

I'll close this for now. It's hard for us to do anything without some kind of consistent repro to work with. I think the bit flip explanation is plausible, but if this issue starts reoccurring consistently, feel free to reopen or file a new issue.

[normcf]

Thanks. Also, if this is a real issue, there will be other people experiencing it and will give more clues. I will comment more if it happens again.