-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AdjustReplayGainTest sometimes segfaults #10497
Comments
Commented by: ywwg I am unable to reproduce on my own machine. Can you figure out what object is segfaulting? is m_pEngineSync null? I suspect this is an initialization race condition that likely only affects this test because it uses an unusual code path. |
Commented by: Holzhaus I actually don't know. I just happened again, but looking at the coredump I doesn't look like m_pEngineSync is null:
All of these seem to exist. My hunch was that |
Commented by: Holzhaus |
Commented by: Holzhaus Just happened again, same issue. |
Commented by: uklotzde Confirmed. Backtrace suggests a race condition when terminating the test. 280/717 Test #515: AdjustReplayGainTest.AdjustReplayGainUpdatesPregain .....................................***Exception: SegFault 1.70 sec
|
Commented by: ywwg I think this is because I'm doing slotLoadTrack instead of loadTrack, which waits for the track to actually load. The test is quitting before the caching reader has a chance to finish |
Commented by: uklotzde Not fixed yet, happened again:
|
Commented by: ywwg Ah, the loadTrack function waits for "istrackloaded", which returns true because the old track was already loaded. It doesn't actually wait to see if the new track is loaded. This is just a problem with signalpathtest.h. I'll fix. |
Issue closed with status Fix Committed. |
Reported by: Holzhaus
Date: 2021-08-19T23:28:54Z
Status: Fix Committed
Importance: Critical
Launchpad Issue: lp1940589
Attachments: adjustreplaygaintestsegfault.coredump.xz
This randomly happens when running tests on main (e.g. 2.4-alpha-767-g0774a046ca).
The text was updated successfully, but these errors were encountered: