Forum

Results 1 to 6 of 6
  1. #1
    Join Date
    January 2010
    Location
    US
    Posts
    4

    Exclamation [Bug] Using terminal service to a machine with the teamspeak client causes hang

    Issue description:
    When connecting to a working teamspeak 3 server and then having another computer terminal service into the teamspeak client computer -- teamspeak will no longer hear teammates talk nor can you speak after disconnecting from the TermService session.

    When the problem happens these things are noticed:
    - When someone attempts to speak the green circle lights up with no voice, but does not unlight when finished speaking.
    - Users can perform other actions within teamspeak such as moving between channels.
    - Once attempting to close teamspeak, the client will hang and you must kill the process from task manager.

    If needed I can attach a crash dump, but seems easy enough to reproduce. Let me know if one is needed though.

    [Machine A] OS: Windows 7 32-bit
    [Machine A] is regarded as steps without noted machine.
    [Machine B] is terminal service client. I have reproduced with Ubuntu and a Windows 7 x64 clients.

    Steps to reproduce:
    1. Winkey + Pause
    2. Advanced system settings
    3. Remote Tab
    4. Check "Allow connections from computers running any version of Remote Desktop"
    5. Select desired users with passwords
    6. [Machine B] Confirm Terminal service connection is functional to [Machine A].
    7. Once functional without terminal service connection -- connect with teamspeak 3 on [Machine A].
    8. (latest server version and client installed)
    9. Confirm able to speak through teamspeak 3 to members.
    10. Minimize teamspeak 3
    11. [Machine B] On terminal service client set to not play sounds on your or the other computer.
    12. [Machine B] Connect to [Machine A].
    13. [Machine B] Browse around and normally use the system a bit.
    14. [Machine B] Disconnect your session.(Not logout)
    15. Login to [Machine A].
    16. Attempt to use teamspeak 3 and speak.
    17. Notice: Your green light does not light, nor can you hear other voices when their green light brightens up.
    18. Attempt to close teamspeak 3 client
    19. Notice: It hangs and you are required to kill the process.

    Expected results:

    1. Sound should reoccur after disconnecting from the terminal service session.
    2. Sound should not occur if terminal service session is set to not to hear sound.
    3. Sound should occur if terminals service session is set to hear sound. (Haven't checked this one though -- good testcase though)

    Actual results:
    - No sound is heard after disconnecting from terminal service no sound session. (This is the bug)
    - No sound is heard during terminal service no sound session. (This is good)

  2. #2
    Join Date
    January 2010
    Location
    US
    Posts
    4
    Maybe I have looked in the wrong spot for a post describing what to do if a bug is found. But is this the correct location so support/devs will know of an issue in their product?

  3. #3
    Join Date
    December 2009
    Location
    Switzerland
    Posts
    439
    Yes, it is the correct location to report bugs. But I am not sure which of the bug reports are read and taken into consideration. I am missing the feedback from the TS team at this point. A short ACK would be great

  4. #4
    Join Date
    June 2008
    Posts
    18,396
    Roger that, please add your dumpfile if it is a 32 bit file.

  5. #5
    Join Date
    January 2010
    Location
    US
    Posts
    4
    It doesn't necessarily crash when the issue happens. Although the application doesn't close when going file/exit. I am forced to kill the process. So here is the breakpoint of the dump of the current process when stuck in this state.

    Thanks dante696 and PeterW -- FIN/ACK

    0:016> !analyze -hang -v
    ************************************************** *****************************
    * *
    * Exception Analysis *
    * *
    ************************************************** *****************************

    ...

    FAULTING_IP:
    ntdll!DbgBreakPoint+0
    77553540 cc int 3

    EXCEPTION_RECORD: ffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 77553540 (ntdll!DbgBreakPoint)
    ExceptionCode: 80000003 (Break instruction exception)
    ExceptionFlags: 00000000
    NumberParameters: 3
    Parameter[0]: 00000000
    Parameter[1]: 85fa3370
    Parameter[2]: 775bd23d

    FAULTING_THREAD: 00000011

    BUGCHECK_STR: HANG

    PROCESS_NAME: ts3client_win32.exe

    ERROR_CODE: (NTSTATUS) 0xcfffffff - <Unable to get error code text>

    EXCEPTION_CODE: (NTSTATUS) 0xcfffffff - <Unable to get error code text>

    EXCEPTION_PARAMETER1: 00000000

    EXCEPTION_PARAMETER2: 85fa3370

    EXCEPTION_PARAMETER3: 775bd23d

    NTGLOBALFLAG: 0

    APPLICATION_VERIFIER_FLAGS: 0

    DERIVED_WAIT_CHAIN:

    Dl Eid Cid WaitType
    -- --- ------- --------------------------
    16 1378.14f4 Speculated (Triage) -->
    17 1378.8b4 Event

    WAIT_CHAIN_COMMAND: ~16s;k;;~17s;k;;

    BLOCKING_THREAD: 000008b4

    DEFAULT_BUCKET_ID: APPLICATION_HANG_BlockedOn_EventHandle

    PRIMARY_PROBLEM_CLASS: APPLICATION_HANG_BlockedOn_EventHandle

    LAST_CONTROL_TRANSFER: from 77565e4c to 775664f4

    STACK_TEXT:
    04d5fd1c 77565e4c 75906872 00000001 04d5fd70 ntdll!KiFastSystemCallRet
    04d5fd20 75906872 00000001 04d5fd70 00000001 ntdll!NtWaitForMultipleObjects+0xc
    04d5fdbc 76bdf12a 04d5fd70 04d5fde4 00000000 KERNELBASE!WaitForMultipleObjectsEx+0x100
    04d5fe04 76bdf29e 00000001 7ffdf000 00000000 kernel32!WaitForMultipleObjectsExImplementation+0x e0
    04d5fe20 73b212da 00000001 04d5fe58 00000000 kernel32!WaitForMultipleObjects+0x18
    04d5fe38 73b22e13 00000001 ffffffff 00000000 dsound!WaitObjectArray+0x17
    04d5ff58 73b4e499 ffffffff 00000000 00000000 dsound!CThread::TpWaitObjectArray+0x51
    04d5ff6c 73b229ae 00000000 01ba0950 73b4e4e9 dsound!CLeapRenderDevice::ThreadProc+0xc
    04d5ff78 73b4e4e9 00000000 73b4e4ae 04d5ff94 dsound!CThread::ThreadLoop+0x1d
    04d5ff80 73b4e4ae 04d5ff94 76be1174 01ba0950 dsound!CThread::PrivateThreadProc+0x32
    04d5ff88 76be1174 01ba0950 04d5ffd4 7757b3f5 dsound!CThread::ThreadStartRoutine+0xd
    04d5ff94 7757b3f5 01ba0950 243699ec 00000000 kernel32!BaseThreadInitThunk+0xe
    04d5ffd4 7757b3c8 73b4e4a1 01ba0950 00000000 ntdll!__RtlUserThreadStart+0x70
    04d5ffec 00000000 73b4e4a1 01ba0950 00000000 ntdll!_RtlUserThreadStart+0x1b


    FOLLOWUP_IP:
    dsound!WaitObjectArray+17
    73b212da 5d pop ebp

    SYMBOL_STACK_INDEX: 5

    SYMBOL_NAME: dsound!WaitObjectArray+17

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: dsound

    IMAGE_NAME: dsound.dll

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bd9fd

    STACK_COMMAND: ~17s ; kb

    BUCKET_ID: HANG_dsound!WaitObjectArray+17

    FAILURE_BUCKET_ID: APPLICATION_HANG_BlockedOn_EventHandle_cfffffff_ds ound.dll!WaitObjectArray

    WATSON_STAGEONE_URL: http://watson.microsoft.com/00033540.htm?Retriage=1

  6. #6
    Join Date
    June 2008
    Posts
    18,396
    This is an old report.
    Is this reproducable anymore?

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. [Bug] Terminal Services confuses client
    By Hssarth in forum Bug Reports [EN/DE]
    Replies: 1
    Last Post: June 22nd, 2010, 01:26 PM
  2. [Bug] Terminal Services confuses client
    By Hssarth in forum Suggestions and Feedback
    Replies: 1
    Last Post: June 22nd, 2010, 01:26 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •