Skip to content
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

Compile Score Timeline has unrelated files listed #25

Open
missmah opened this issue Jun 20, 2022 · 4 comments
Open

Compile Score Timeline has unrelated files listed #25

missmah opened this issue Jun 20, 2022 · 4 comments
Labels
bug Something isn't working

Comments

@missmah
Copy link

missmah commented Jun 20, 2022

image

The files listed in the timeline aren't related to or included by each other -- it seems like maybe the database got corrupted, or somehow a pointer to a data structure is pointing to the wrong element.

Here, we see one cpp file ostensibly including a couple of totally separate CPP files (which in reality are not included by each other), and eventually building some bullet code -- which, again, is unrelated to everything above it in this hierarchy.

@missmah
Copy link
Author

missmah commented Jun 20, 2022

More information about this bug. I restarted CompileScore and reloaded the file, and the data I'm seeing is different (and consistent/sane again).

I had been clicking Actions -> Reload previously, which worked like a charm on Friday night -- but it seems to have failed me just now today.

@Viladoman
Copy link
Owner

This is really concerning!
If I understand properly, same recorded data looked wrong and then right again? meaning it is an issue with the viewer and not the .scor generator?

@missmah
Copy link
Author

missmah commented Jun 21, 2022

Yeah, seems to be a viewer issue, and it seemed like it was showing a garbage interpretation of the data after Reload, and then I quit and re-launched, and everything looked correct. But Reload had worked fine hundreds of times before that.

I did put the machine to sleep over the weekend; but, it also has ECC memory, so I wouldn't expect it to be due to a cosmic ray style flipped bit...

@Viladoman Viladoman added the bug Something isn't working label Jun 22, 2022
@Viladoman
Copy link
Owner

I am thinking that maybe the timeline logic did not properly clear the previous tree and merged 2 different timelines together.
I think cosmic rays is less probable than a human error in this case :D. I will have a look.
Thanks for letting me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants