CPU Maxed Out

[kixelated]

https://discord.com/channels/1124083992740761730/1151177897537699951/1452395494193238057

I'm noticing something odd with hang v0.9.1: the track consumer seems to enter a tight loop, effectively bringing everything to a halt with the CPU spinning at 100%.

Type: cpu
Time: 2025-12-21 20:09:09 CET
Duration: 30s, Total samples = 16.01s (53.36%)
Showing nodes accounting for 14.06s, 87.82% of 16.01s total
Dropped 601 nodes (cum <= 0.08s)
flat flat% sum% cum cum%
5.42s 33.88% 33.88% 13.22s 82.59% hang::model::track::TrackConsumer::read_frame::{{closure}}::{{closure}}
3.06s 19.12% 53.00% 7.80s 48.71% hang::model::group::GroupConsumer::buffer_until::{{closure}}
2.88s 17.98% 70.98% 3.26s 20.38% hang::model::group::GroupConsumer::read::{{closure}}

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Related PRs

moq-dev/gst#27 - Update to hang 0.9.0 / moq-lite 0.10.1 / moq-native 0.10.1 [closed]

👤 Suggested Assignees

• davegullo

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[kixelated]

Fixed with the OrderedConsumer changes.