• Hey Guest, we're evolving the future of TeaSpeak.
    You're invited to join the discussion here!

Search results

  1. REDOSS

    Pending i cannt upload icons

    // Closed.
  2. REDOSS

    Pending bug permissions all versions

    // Closed.
  3. REDOSS

    Pending Packet problem

    // Closed.
  4. REDOSS

    Pending file transfer server quota exceeded

    // Closed
  5. REDOSS

    Pending TeaSpeak all versions ?

    It is not a software bug, I close the topic. // Closed.
  6. REDOSS

    Server Crash

    Crash dumps of these versions are not considered, use the latest version of the server. Too many changes were made and it will be problematic to disassemble the dump.
  7. REDOSS

    Pending error old version

    // Closed.
  8. REDOSS

    Pending old version error

    // Closed.
  9. REDOSS

    TeaClient Crash

    Moved to TeaWeb / TeaClient section.
  10. REDOSS

    Pending Processor

    In my opinion, there is a RAM leak in version 1.5.6, it does not always occur. Once I met a leak only on the 16th day of work, and the next time on the 4th day of work. The increased CPU consumption is caused by a RAM leak in my case.
  11. REDOSS

    My server after restart doesnt start

  12. REDOSS

    Crash version 1.4.22

    1.5.6 or 1.5.6-beta-1? These versions are still the same, but I will still clarify just in case.
  13. REDOSS

    Pending Screen sharing

    // Closed.
  14. REDOSS

    Crash version 1.4.22

    BTW, today the version was slightly updated, without forming a new build. The list of changes can be found here.
  15. REDOSS

    Pending TeaSpeak No insufficient client permissions on Kick

    // Fixed && Closed. Use version 1.5.6
  16. REDOSS

    Pending Screen sharing

    // Closed.
  17. REDOSS

    Pending bug Query Group

    // Fixed && Closed.
  18. REDOSS

    Pending It is bug or It is new version ?

    // Fixed && Closed.
  19. REDOSS

    Crash version 1.4.22

    Version 1.5.6 works very well at the moment, with no crashes and no memory leaks.
  20. REDOSS

    Pending What is the reason for this error?

    This should be fixed in version 1.5.6. As I said above. Comparison with 22 clients is not critical, so you can test version 1.5.6 on higher loads.