Skip to content
This repository has been archived by the owner on Feb 12, 2023. It is now read-only.

Audio calls can cause memory corruption #35

Closed
tux3 opened this issue Jun 30, 2014 · 7 comments
Closed

Audio calls can cause memory corruption #35

tux3 opened this issue Jun 30, 2014 · 7 comments
Labels
C-bug The issue contains a bug report

Comments

@tux3
Copy link
Member

tux3 commented Jun 30, 2014

No description provided.

@tux3 tux3 added the bug label Jun 30, 2014
@dubslow
Copy link
Contributor

dubslow commented Jul 6, 2014

How well do you have this tracked down? I can throw a full blown debugging run at it...

@tux3
Copy link
Member Author

tux3 commented Jul 6, 2014

Barely. It's pretty hard to track down.

@msteinbeck
Copy link
Contributor

The new Audiobuffer based on a non locking circular ringbuffer will be ready soon.

@tux3
Copy link
Member Author

tux3 commented Jul 6, 2014

I just found out that I'm completely retarded and my QTimers and other call objects are happilly living in the wrong thread.
This could explain the corruption and/or pulseaudio crashes since this is not even supposed to work and explicitely forbidden by Qt.

@tux3
Copy link
Member Author

tux3 commented Jul 6, 2014

Actually, I might just have fixed the memory corruption with 6ba8be3

I've had an audio call last 10 minutes (and still going) without crashing on Windows.

If nobody can reproduce anymore, I'll close this bug.

@msteinbeck
Copy link
Contributor

This commit fixes some bugs I had some problems with for the ringbuffer, very nice!

@tux3
Copy link
Member Author

tux3 commented Jul 7, 2014

It seems to be fixed. Finally.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
C-bug The issue contains a bug report
Projects
None yet
Development

No branches or pull requests

3 participants