Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • J jami-client-gnome
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 88
    • Issues 88
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinux
  • jami-client-gnome
  • Issues
  • #397

Closed
Open
Created Dec 04, 2015 by RingBot@RingBotOwner

Infinite loop using alsa

Issue generated from Tuleap's migration script. Originally submitted by: Emmanuel Lepage Vallee (elv13)

Here is one of the possible infinite loop with the alsa backend

[1449225107.948|32305|alsalayer.cpp:690 ] Audio: Mic error: Broken pipe
[1449225107.952|32305|alsalayer.cpp:690 ] Audio: Mic error: Broken pipe
[1449225107.955|32305|alsalayer.cpp:690 ] Audio: Mic error: Broken pipe
[1449225107.959|32305|alsalayer.cpp:690 ] Audio: Mic error: Broken pipe
[1449225107.963|32305|alsalayer.cpp:690 ] Audio: Mic error: Broken pipe
[1449225107.970|32305|alsalayer.cpp:690 ] Audio: Mic error: Broken pipe
[1449225107.973|32305|alsalayer.cpp:690 ] Audio: Mic error: Broken pipe

[...]

I guess it has to do with dring losing the audio while running. After this, dring has to be restarted or will eat the CPU.

It happen "randomly" when using the computer. If you let dring run for long enough and use a web browser, it will happen.

Assignee
Assign to
Time tracking