Skip to content

Fix #4290 beam span crash by switching to shared_ptr#4291

Closed
infojunkie wants to merge 1 commit intorism-digital:developfrom
infojunkie:fix-4290-renderToTimemap-crashes
Closed

Fix #4290 beam span crash by switching to shared_ptr#4291
infojunkie wants to merge 1 commit intorism-digital:developfrom
infojunkie:fix-4290-renderToTimemap-crashes

Conversation

@infojunkie
Copy link
Contributor

@infojunkie infojunkie commented Mar 5, 2026

Fix #4290 beam span crash in expansion, by switching to shared_ptr which takes care of reference counting the pointers and deleting them.

@lpugin
Copy link
Contributor

lpugin commented Mar 6, 2026

Thanks. I still want to find where the pointer is not handled correctly.

@lpugin lpugin closed this in 5f7bb9d Mar 6, 2026
@lpugin
Copy link
Contributor

lpugin commented Mar 6, 2026

I fixed it. It was missing an override of the Object::CloneReset. Thanks for helping tracking this down.

@infojunkie infojunkie deleted the fix-4290-renderToTimemap-crashes branch March 6, 2026 17:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

renderToTimemap crashes (SIGSEGV in BeamSpan::ClearBeamSegments) when a cross-barline beam is in the same measure as a backward repeat barline

2 participants