Pocho Azul | 21 Feb 2021 11:14 a.m. PST |
I have noticed that sometimes unrelated threads from two different boards seem to get mashed together. For example, a recent thread titled "Best brush-on primer?" from the Painting board, is interleaved with an unrelated thread from the Modern Battle Reports board titled "Missile Threat AAR." Both threads appear listed as separate in threads in the MBR board, but only the primer thread appears in the Paint board. Opening the combined thread has dual "Back to" links leading to both boards. I have noticed similar mashed up threads before, but this is the first time I realized what was going on, and looked into it. I can post screens, if this would be helpful. Just thought you ought to know. |
ZULUPAUL  | 21 Feb 2021 12:04 p.m. PST |
Yup known as "The Bug" an ongoing & long standing problem.🦟 |
MajorB | 21 Feb 2021 12:11 p.m. PST |
Caused by a race condition in the code when two threads are updated at the same time. |
Pocho Azul | 21 Feb 2021 12:40 p.m. PST |
|
Schogun | 21 Feb 2021 2:49 p.m. PST |
To make matters worse, my "Best Brush-On Primer?" post doesn't show up on my Front Page. I have to search for it. This happens a lot when I post a new topic. |
Waco Joe | 21 Feb 2021 3:30 p.m. PST |
Embrace the Bug. The Bug is your friend. |
d88mm1940 | 21 Feb 2021 6:19 p.m. PST |
I thought that it was caused by Russians or Democrats snooping around… |
Extra Crispy  | 21 Feb 2021 9:31 p.m. PST |
It's the Jewish space lasers… |
Editor in Chief Bill  | 21 Feb 2021 10:40 p.m. PST |
Caused by a race condition in the code when two threads are updated at the same time. Nope, try again.  Pocho Azul – if you hit the Complaint button on such topics, I can usually fix them. Sometimes, I can only save one of the topics. Depends on the nature of the mash-up. |
pzivh43  | 22 Feb 2021 8:53 a.m. PST |
It's a feature, not a Bug. The cognitive dissonance helps shake up your synapses and keeps the brain from getting all clogged up! |
etotheipi  | 22 Feb 2021 9:23 a.m. PST |
Caused by a race condition in the code when two threads are updated at the same time. Nope, try again. 
It appears that the thread creation mechanism does not have atomic control over the allocation of new thread indices. As a result, when two threads get to the part of thread creation where they request an index, they get the same one. Close enough? ;) |
Editor in Chief Bill  | 22 Feb 2021 2:58 p.m. PST |
Close enough? ;) Nope. It is not an "at the same moment" bug. |
Pocho Azul | 22 Feb 2021 9:10 p.m. PST |
if you hit the Complaint button on such topics, I can usually fix them. Sometimes, I can only save one of the topics. Depends on the nature of the mash-up. OK, that's what I will do next time I see one (assuming I do). Thanks. |
etotheipi  | 23 Feb 2021 3:06 p.m. PST |
Nope. It is not an "at the same moment" bug. Lack of atomic control doesn't have to be "simultaneous" or even close in time. |