Skip to content
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

Consistent crash when loading a different device set preset #2332

Open
murrayn opened this issue Nov 15, 2024 · 4 comments · May be fixed by #2342
Open

Consistent crash when loading a different device set preset #2332

murrayn opened this issue Nov 15, 2024 · 4 comments · May be fixed by #2342

Comments

@murrayn
Copy link

murrayn commented Nov 15, 2024

The crash happens reliably when loading a new device set preset while the SDR is running. If the SDR is stopped before loading a device set preset the crash does not occur.

sdrangel_7.22.4_ubuntu-22.04

Here is an example trace: sdrangel-log.txt

@srcejon
Copy link
Collaborator

srcejon commented Nov 15, 2024

Can you attach the preset as well please?

@murrayn
Copy link
Author

murrayn commented Nov 16, 2024

It's not dependent on any particular preset. It's also been an issue for me for a long time, just never got around to reporting it. I just work around it by stopping the SDR before switching presets. It could be my hardware, an old V3 rtl-sdr. I just thought the trace might give some clue, although I didn't see anything that stood out to me.

@f4exb
Copy link
Owner

f4exb commented Nov 16, 2024

Is this an issue to stop the device before loading a new preset?

@srcejon
Copy link
Collaborator

srcejon commented Nov 16, 2024

Crash appears to be in DSPDeviceSourceEngine::handleMessage for a DSPSignalNotification - the list of m_basebandSampleSinks is no longer valid.

Is this an issue to stop the device before loading a new preset?

For this and #2315, it might be simpler if we just stop the device first.

srcejon added a commit to srcejon/sdrangel that referenced this issue Nov 26, 2024
@srcejon srcejon linked a pull request Nov 26, 2024 that will close this issue
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 a pull request may close this issue.

3 participants