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

Issues causing FreeDV 1.4 release candidate to crash #34

Merged
merged 2 commits into from
Dec 25, 2019

Conversation

drowe67
Copy link
Owner

@drowe67 drowe67 commented Nov 18, 2019

Some issues causing freedv-gui to crash, that were found by the UK team. Anything that causes crashes should be fixed for the FreeDV 1.4 release:

  1. assert() that is firing on Windows machines, was pretty benign, just testing an assumption about a FIFO having space that can tracked down later.
  2. When USB sound devices are changes, and Start is pressed without re running Tools/Audio Config, freedv-gui crashes. OK have reproduced this one on Linux, but no quick fix, so have posted as Issue Crashing when USB devices removed #35

@drowe67 drowe67 changed the title removing assert that is firing on Windows machines testing 1.4 Issues causing FreeDV 1.4 release candidate to crash Nov 19, 2019
@@ -4094,8 +4094,6 @@ void txRxProcessing()
fprintf(stderr, " nout: %d\n", nout);
}
ret = codec2_fifo_write(cbData->outfifo1, outsound_card, nout);
// should never fire as we check there is enough room before entering while loop
assert(ret != -1);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I actually just noticed this on OSX as well (happens the instant I push PTT) and it appears it's related to sample rate mismatches. For instance, my Griffin iMic USB sound card seems to default to 48000Hz while my MacBook Pro's internal sound card defaults to 44100. Setting both to 44100 in the app causes the crash not to occur.

Anyway, I haven't dug too much into the Codec2 end of things but does removing the assertion result in other side effects?

Copy link
Owner Author

@drowe67 drowe67 Dec 14, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No it's just checking an assumption about how many samples are in a FIFO. The current Windows Beta has been built off this branch, and has been working OK for a several weeks.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool. I'm fine with this fix, then. I'll see about building a new OSX image with it as well.

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.

None yet

2 participants