Profile

  • Guest
    0
  • Posts: 21
  • Post Likes: 3765

Notifications

  • No Unread Notifications

Unresolved
Suspected race condition in Lap Record write operation

This thread is closed. Threads older than 6 weeks are closed automatically. To continue this discussion, create a new thread.
1
This topic has been closed by the moderator
5000
4 years 326 days ago
What did you try to do?
Check the race lap record of Monaco.

What happened instead?
The circuit overview tab of the race lap record says the lap record is 1:14.729, but it actually should be 1:14.703.
Screenshots:



Did the problem happen while using wi-fi, mobile data, or both?
Wi-fi

Did the bug happen in the app, on PC, or both?
PC

What operating system is your PC?
Windows 10

Which browser did you experience the problem in?
Microsoft Chromium Edge

Can the bug be reproduced?
I only picked one instance of this bug. This same bug occurs on many other Lap Records, such as Monaco quali and China quali.

Additional comments:
As I alluded to in the subject line, I suspect this is caused by a "race condition" caused by the write operation not being atomic (yes, I'm a programmer).
This seems to only happen when the correct lap record and the erroneous lap record are set in the same race (which is why I suspect it's a race condition. I hope you can write a script to loop through all of these 50 race IDs to fix this, and patch the code that caused this so it doesn't happen in the future.
5000
4 years 321 days ago
Cough... 1:14.588 :D :D

But yeah, seems like there was a bug for sure?
This topic has been closed by the moderator
1

You must be logged in to post a reply.

This site uses cookies. By continuing to browse the site you are agreeing to its use of cookies. Read our Privacy Policy