Rogue Frames Randomly Output from PresentData in P00 ETL

未关闭
#556 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
停滞
技术栈
cpp

调研方向

Start by reading PresentData’s handling of the completed queue and how frames are marked ready; the issue does not name files or tests. Compare the end-of-capture base case with the failure case, where the extra frames are both added to completed and marked ready. Done means identifying the circumstances that distinguish the cases and explain the 24 extra frames.

由索引模型根据 Issue 内容生成。

描述

Randomly get 24 extra frames from P00Heaven. All frames have time in present = 0. Shows in legacy Streamer, new broadcaster, and Main pre-rework. Frames appear to have plausible timestamps for being legitimate.

race condition exists in PresentData. I was expecting something in how service is consuming from the completed queue. But in the normal case presentdata is not marking those frames as complete, and in the failure case it is. so the service is just processing what it gets (as it should), and it is probably presentdata misbehaving somehow by randomly choosing to spit these frames out.

we can see that in either case, the weird frames are added to completed
the difference comes in the failure case, they're also marked ready, but not marked in the base case

Seems limited to this ETL and only affects end of capture. Analyze later to determine discriminating circumstances for the base case and the 24 extra frame case.

主要语言
C++
星标
2.6k
派生
201
平均合并
2 天 21 小时
30 天内合并 PR
16

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

GameTechDev/PresentMon 的其他 Issue

查看 GameTechDev/PresentMon 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。