Forum

Page 2 of 2 FirstFirst 12
Results 16 to 30 of 30
  1. #16
    Join Date
    June 2008
    Posts
    18,003
    Quote Originally Posted by Gnarfoz View Post
    This still happens, with client 3.0.8. (And 3.0.7 before it, too.)

    Edit by a moderator
    Please do not rename the crashdump file! It makes it hard to find out, what client version you use!
    Please give us mor informations, your crashdump is currently useless for us. Do not rename it please.

    - Please make sure, that you use client 3.0.8 (16.07.2012 08:56:53)
    - Try the IP of that server 188.40.37.111:9987 instead h********.net
    - Deactivate your plugins and try to connect to your server with h**********.net
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  2. #17
    Join Date
    July 2010
    Location
    Germany
    Posts
    27
    I renamed nothing, that's the original file name from C:\Users\<username>\AppData\Local\CrashDumps.
    Also, I included the regular client log from that particular crash with the dump in the zip archive. That has the version and a pretty precise build date in the first line. So while indeed it doesn't have the build number in the version string, I doubt that makes it "useless".
    Maybe the different file name stems from the fact that my install uses the "settings in application folder" option. Someone else, whose settings are stored in their user profile, found their crash dump files in their "My Documents" folder, with the file name you desire ("ts3_clientui-win64-1327056547-2012-01-26 19_29_03.905650" etc.).

    In any case: as can easily be gathered from the log file, this was not the 2012-07-16 build, but a beta build from 2012-07-12. Since this particular crash happened on 2012-07-12 19:38 (see file timestamp and log), this is not surprising.

    Still, even though there's nothing in the changelog that would indicate any such bug was fixed between then and now, I'm happy to discard the entire thing as "useless" on the basis of "not the current version now", since I'm aware of how much bug hunting sucks.


    To your suggestions:

    I'll try, but since these servers are auto-connect bookmarks, the client crashes almost immediately on startup as soon as this behaviour has manifested. I'll see about then editing the bookmarks.ini to turn that off and try the IP instead of the hostname. Changing either one beforehand would a) falsify the situation (that would indeed be "useless"!) and b) be annoying to use.


    Lastly, I'll just restate this, since it could lead an inquisitive developer to the right thing with or without CrashDumps or logs:
    When this behaviour sets in, installing client 3.0.2 (no newer versions) "fixes" it. Both in the manner that no newer client versions will start, but also, more curiously, in that after you've run 3.0.2 for a while, you can once again upgrade to whatever the latest version is, and it will work again. For a while, until the cycle repeats.
    So something, somewhere must get left behind that the 3.0.2 client ignores, and/or cleans up. The clean up part doesn't necessarily have to be true, it could also be something that times out or gets invalidated later on. Stale connections, config or log files, registry keys even - you know your own code best.

    As for the environment:
    Win7 x64, x64 Client, TS3 installed in a non-UAC protected folder, settings in application folder. The server (most recent available Linux x64 version usually) listens on the default port, there's no TSDNS running, no SRV entries present (support for that didn't exist in 3.0.3 anyway), it's an IDN domain and there's one other virtual server on another port.


    I hope this post was thorough enough to illustrate how frustrating this problem is to anyone affected - it basically means that, so far, we're all stuck on 3.0.2. :-(

  3. #18
    Join Date
    June 2008
    Posts
    18,003
    We need the exact build date, this is the reason, why the filename is important.
    Our developers create several versions per day and we have some older beta releases with vrsion 3.0.7 and 3.0.8.

    This is how it should look like.
    Code:
    ts3_clientui-win64-1342421813-2012-07-18 08_58_57.093986.dmp
    ts3_clientui-win32-1342421813-2012-07-18 08_58_57.093986.dmp
    2012-01-26 < this is to old for us and not the latest client.
    Please send us a crashdump from the latest client, that can be used from our developers.

    The log showed, that yor client was connected to the server, it crashed afterwards, so we guess it is somethign that happens when the client loads channels or somethign else.
    Last edited by dante696; July 19th, 2012 at 07:54 AM.
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  4. #19
    Join Date
    July 2010
    Location
    Germany
    Posts
    27
    Quote Originally Posted by dante696 View Post
    This is how it should look like.
    Code:
    ts3_clientui-win64-1342421813-2012-07-18 08_58_57.093986.dmp
    ts3_clientui-win32-1342421813-2012-07-18 08_58_57.093986.dmp
    I can't give you what's not there. :\
    Does Windows generate this for you, or is it a feature of TeamSpeak itself?
    I ventured a guess as to why they are in C:\Users\<username>\AppData\Local\CrashDumps instead of "My Documents" (and have a different name). Any ideas?

    Quote Originally Posted by dante696 View Post
    2012-01-26 < this is to old for us and not the latest client.
    Please send us a crashdump from the latest client, that can be used from our developers.
    You realize this is someone else's filename I just mentioned additionally?
    The dump I submitted is from a very recent version!

    Quote Originally Posted by dante696 View Post
    The log showed, that yor client was connected to the server, it crashed afterwards, so we guess it is somethign that happens when the client loads channels or somethign else.
    Entirely possible. Would some kind of debug info/server configuration dump help? If so, what exactly?
    Last edited by Gnarfoz; July 20th, 2012 at 08:55 PM. Reason: addendum

  5. #20
    Join Date
    June 2008
    Posts
    18,003
    -_- As said twice, only the crashdump generated from our client with the exact build date does help here.
    And your log file did not show a crash on connect, because your client was connected.
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  6. #21
    Join Date
    July 2010
    Location
    Germany
    Posts
    27
    You keep repeating that as if I did not write anything else.
    Did you actually read my entire post? I've gone over each of your points and asked several questions that, if answered, could keep this keep this thread going in a meaningful direction and hopefully help find and squash the bug, one day.

    I still can't fathom how it could possibly be that you cannot resolve the build number from the version string that actually includes build date and time, but since you keep repeating that it's impossible, I give up.
    Maybe, instead, you could elaborate on how I can make Windows create these in the form that you want?
    It must be some setting, since I doubt Windows 7 Ultimate creates different crash dumps than Windows 7 Professional.

    ------------------merged------------------

    By the way, no matter how many builds the developers generate per hour (...), there's only a few handful of builds at all on your FTP mirrors for the updater to grab:

    http://ftp.4players.de/pub/hosted/ts...nt/1342099233/
    It appears there was only one version available on that day to the updater...
    And if that number is really the "build number" you keep asking for, then suprise, that's just the date & time when the build process was started, as a UNIX time stamp.
    Easy enough to deduce, since a date just two minutes later is in the digitally signed code timestamp on the binary file and a date 5 seconds later than that will show up in WinDbg, if you open the crash dump I supplied in the first place (no I don't have the appropriate symbol definition files, it's not magic).

    ------------------merged------------------

    And suddenly, WinDbg is able to make heads and tails of this, just by putting the old client executable in place:

    Enjoy:

    Code:
    WARNING: Whitespace at start of path element
    
    Loading Dump File [E:\temp\ts3client_win64.exe.744.dmp]
    User Mini Dump File: Only registers, stack and portions of memory are available
    
    Symbol search path is: srv*D:\Programme\Microsoft\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: srv*
    Windows 7 Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: SingleUserTS
    Machine Name:
    Debug session time: Thu Jul 12 19:38:04.000 2012 (UTC + 2:00)
    System Uptime: not available
    Process Uptime: 0 days 0:00:05.000
    ................................................................
    ...............
    Loading unloaded module list
    ............
    This dump file has an exception of interest stored in it.
    The stored exception information can be accessed via .ecxr.
    (2e8.bd4): Unknown exception - code c0000417 (first/second chance not available)
    ntdll!NtWaitForMultipleObjects+0xa:
    00000000`77b018ca c3              ret
    0:000> .ecxr
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ts3client_win64.exe - 
    rax=000000000012b050 rbx=0000000000000000 rcx=000000000012b050
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=0000000140619b88 rsp=000000000012b530 rbp=0000000000000000
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
    r11=000000000012afb0 r12=000000000214cb00 r13=0000000000000000
    r14=0000000000000003 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246
    ts3client_win64!celt_decoder_create+0x290e8:
    00000001`40619b88 488b5c2440      mov     rbx,qword ptr [rsp+40h] ss:00000000`0012b570=2200000000000000
    0:000> !analyze
    *******************************************************************************
    *                                                                             *
    *                        Exception Analysis                                   *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for QtCore4.dll - 
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for QtGui4.dll - 
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for directsound_win64.dll - 
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for windowsaudiosession_win64.dll - 
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for appscanner_plugin.dll - 
    Probably caused by : ts3client_win64.exe ( ts3client_win64!celt_decoder_create+290e8 )
    
    Followup: MachineOwner
    ---------
    
    0:000> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Exception Analysis                                   *
    *                                                                             *
    *******************************************************************************
    
    
    FAULTING_IP: 
    ts3client_win64!celt_decoder_create+290e8
    00000001`40619b88 488b5c2440      mov     rbx,qword ptr [rsp+40h]
    
    EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 0000000140619b88 (ts3client_win64!celt_decoder_create+0x00000000000290e8)
       ExceptionCode: c0000417
      ExceptionFlags: 00000001
    NumberParameters: 0
    
    PROCESS_NAME:  ts3client_win64.exe
    
    ERROR_CODE: (NTSTATUS) 0xc0000417 - An invalid parameter was passed to a C runtime function.
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000417 - An invalid parameter was passed to a C runtime function.
    
    NTGLOBALFLAG:  0
    
    APPLICATION_VERIFIER_FLAGS:  0
    
    APP:  ts3client_win64.exe
    
    FAULTING_THREAD:  0000000000000bd4
    
    BUGCHECK_STR:  APPLICATION_FAULT_STATUS_INVALID_CRUNTIME_PARAMETER_AFTER_CALL
    
    PRIMARY_PROBLEM_CLASS:  STATUS_INVALID_CRUNTIME_PARAMETER_AFTER_CALL
    
    DEFAULT_BUCKET_ID:  STATUS_INVALID_CRUNTIME_PARAMETER_AFTER_CALL
    
    LAST_CONTROL_TRANSFER:  from 0000000140622b59 to 0000000140619b88
    
    STACK_TEXT:  
    00000000`0012b530 00000001`40622b59 : 00000000`00000022 ffffffff`ffffffff 00000000`053c2220 00000000`00000001 : ts3client_win64!celt_decoder_create+0x290e8
    00000000`0012b570 00000001`401b9e0d : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`020fecd0 : ts3client_win64!celt_decoder_create+0x320b9
    00000000`0012b5b0 00000001`402d8e67 : 00000000`020e68c0 00000000`00000001 00000000`00000000 00000000`04dee810 : ts3client_win64+0x1b9e0d
    00000000`0012b960 00000001`40305a49 : 00000000`00000000 00000000`020de320 00000000`00000044 00000000`020de320 : ts3client_win64+0x2d8e67
    00000000`0012bc10 00000000`671151b9 : 00000000`020de320 00000000`02bb2160 00000000`000000ac 00000000`0012be18 : ts3client_win64+0x305a49
    00000000`0012bde0 00000000`67119f21 : 00000000`04dee7f0 00000000`00000002 00000000`00000004 00000000`04dee7f0 : QtCore4!QMetaObject::activate+0x2f9
    00000000`0012be90 00000000`671135f8 : 00000000`02b78b40 00000000`02b78b40 00000000`00000000 00000000`00330000 : QtCore4!QTimer::timerEvent+0xd1
    00000000`0012bec0 00000000`6501d842 : 00000000`0012fae0 00000000`01dd9de0 00000000`04dee7f0 00000000`0012c408 : QtCore4!QObject::event+0x58
    00000000`0012c0c0 00000000`6501f37f : 00000000`00000008 00000000`0012fae0 00000000`0012c400 00000000`0012c408 : QtGui4!QApplicationPrivate::notify_helper+0x102
    00000000`0012c0f0 00000000`67100994 : 00000000`01ddb100 00000000`01f59040 00000000`0012c460 00000000`00000002 : QtGui4!QApplication::notify+0x23f
    00000000`0012c390 00000000`671253ce : 00000000`01ddb1a8 00000000`00181000 00000000`0018100c 00000000`04dd2560 : QtCore4!QCoreApplication::notifyInternal+0x74
    00000000`0012c3e0 00000000`67125b52 : 00000000`0400000b 00000000`00000113 00000000`00000000 00000000`00000000 : QtCore4!QEventDispatcherWin32::interrupt+0x55e
    00000000`0012c440 00000000`779c9bd1 : 00000000`00000000 00000000`00000000 00000000`0000fffd 00000041`00000000 : QtCore4!QEventDispatcherWin32::event+0x5f2
    00000000`0012c4f0 00000000`779c98da : 00000000`0012c660 00000000`67125970 00000000`0012fa18 00000000`0088a9c0 : user32!UserCallWinProcCheckWow+0x1ad
    00000000`0012c5b0 00000000`67128155 : 00000000`01f56d40 00000000`01f56d40 00000000`67125970 00000000`00000001 : user32!DispatchMessageWorker+0x3b5
    00000000`0012c630 00000000`65081ed5 : 00000000`01f56d40 00000000`0012fa18 00000000`0012fa00 00000000`0012fa78 : QtCore4!QEventDispatcherWin32::processEvents+0x875
    00000000`0012f9e0 00000000`6710000e : 00000000`01f59040 00000000`00000024 00000000`01f59081 00000000`00000008 : QtGui4!QApplicationPrivate::translateTouchEvent+0x8c5
    00000000`0012fa10 00000000`671044e0 : 00000000`00000024 00000000`01f59040 00000001`40000000 00000001`40000000 : QtCore4!QEventLoop::exec+0x13e
    00000000`0012fa50 00000001`40359169 : 00000000`00000000 00000000`ffffffff 00000001`40000000 00000000`04c1beb8 : QtCore4!QCoreApplication::exec+0xe0
    00000000`0012faa0 00000001`40623fb5 : 00000000`00000000 00000000`00000000 00000001`40000000 00000001`40000000 : ts3client_win64+0x359169
    00000000`0012feb0 00000000`773e652d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ts3client_win64!celt_decoder_create+0x33515
    00000000`0012ff60 00000000`77adc521 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0xd
    00000000`0012ff90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d
    
    
    STACK_COMMAND:  ~0s; .ecxr ; kb
    
    FOLLOWUP_IP: 
    ts3client_win64!celt_decoder_create+290e8
    00000001`40619b88 488b5c2440      mov     rbx,qword ptr [rsp+40h]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  ts3client_win64!celt_decoder_create+290e8
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: ts3client_win64
    
    IMAGE_NAME:  ts3client_win64.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ffecf83
    
    FAILURE_BUCKET_ID:  STATUS_INVALID_CRUNTIME_PARAMETER_AFTER_CALL_c0000417_ts3client_win64.exe!celt_decoder_create
    
    BUCKET_ID:  X64_APPLICATION_FAULT_STATUS_INVALID_CRUNTIME_PARAMETER_AFTER_CALL_ts3client_win64!celt_decoder_create+290e8
    
    WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/ts3client_win64_exe/3_0_8_0/4ffecf83/ts3client_win64_exe/3_0_8_0/4ffecf83/c0000417/00619b88.htm?Retriage=1
    
    Followup: MachineOwner
    ---------
    ts3client_win64!celt_decoder_create
    Last edited by dante696; July 24th, 2012 at 07:35 AM.

  7. #22
    Join Date
    June 2008
    Posts
    18,003
    The fact, that this was no crashdump from our client stays.....

    A dump file from windows is not usefull for our developers. It does not know the "symbols" that we use in our client.
    Example: *** ERROR: Symbol file could not be found. Defaulted to export symbols for QtCore4.dll -

    One last time, please deliever us the crashdump file generated from our client with name. We can not analyze from sucha dump file.
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  8. #23
    Join Date
    July 2010
    Location
    Germany
    Posts
    27
    I'm going to make this really simple:

    There are no crash dumps in my "My Documents" folder (as per The Crashdump thread).

    What now?

  9. #24
    Join Date
    July 2002
    Location
    Germany
    Posts
    2,192
    Hi,

    without a crash dump or a way to reproduce the problem there is very little we can do . Sorry.

  10. #25
    Join Date
    July 2010
    Location
    Germany
    Posts
    27

    Arrow

    So, since this is still happening, and server 3.0.7 is going to require client 3.0.10+, I'm taking another shot at it.

    To reiterate:
    Ever since 3.0.3, after a variable amount of time* connected to a server, the client starts crashing when connecting to *any* server (not just ours). You can still start the client fine, if you don't have any auto-connect bookmarks. The crash happens immediately after connecting. After this situation has arisen, downgrading to 3.0.2 (restoring backed up config files along the way, since 3.0.4 converts the config files to SQLite and deletes the old files) makes connecting possible again. And after a while* it's also possible to upgrade to a newer version again, until the cycle begins again.

    * What you have to do to trigger this problem is still a mystery. I once attributed it to getting disconnected by my ISP while connected to my server, but more recent tests have shown it can also happen right after updating from 3.0.2 to something newer, without any network interruptions.


    One of the further observations I made is that deleting *everything* but settings.db in the config folder... changes nothing.
    Deleting *just* settings.db fixes it.

    So a pretty simple deduction might be that it's something in settings.db causing it.


    After examining 3 different states of the settings.db SQLite DB, I so far haven't found any outstanding differences, however, some of the data is stored in not very human-readable format, so it's very likely I'm overlooking something.

    I examined a db from a working 3.0.2 setup, one grabbed after installing 3.0.10 and one that 3.0.10 recreates when the file is missing (because I deleted it).



    Further: taking another look at crashdumps the offending instruction pointer at the time of the crash is always "ts3celt_celt_decoder_create+2aa18" with the error code and exception code being "0xc0000417 - An invalid parameter was passed to a C runtime function."

    The build number is 1354873317.
    I'll quote the WinDbg output of one here for posterity, but I'll attach 8 of them, to prove my point.

    Code:
    Microsoft (R) Windows Debugger Version 6.2.8400.0 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Christian\AppData\Local\CrashDumps\ts3client_win64.exe.13888.dmp]
    User Mini Dump File: Only registers, stack and portions of memory are available
    
    Symbol search path is: srv*D:\Programme\Microsoft\Symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: srv*
    Windows 7 Version 7601 (Service Pack 1) MP (8 procs) Free x64
    Product: WinNt, suite: SingleUserTS
    Machine Name:
    Debug session time: Mon Jan  7 19:22:56.000 2013 (UTC + 1:00)
    System Uptime: not available
    Process Uptime: 0 days 0:00:35.000
    ................................................................
    ...............
    Loading unloaded module list
    ..............
    This dump file has an exception of interest stored in it.
    The stored exception information can be accessed via .ecxr.
    (3640.2788): Unknown exception - code c0000417 (first/second chance not available)
    ntdll!NtWaitForMultipleObjects+0xa:
    00000000`771e18ca c3              ret
    0:000> .ecxr
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ts3client_win64.exe - 
    rax=000000000012ad60 rbx=0000000000000000 rcx=000000000012ad60
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=0000000140698338 rsp=000000000012b240 rbp=0000000000000000
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
    r11=000000000012acc0 r12=0000000005111c70 r13=0000000000000000
    r14=0000000000000006 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246
    ts3client_win64!ts3celt_celt_decoder_create+0x2aa18:
    00000001`40698338 488b5c2440      mov     rbx,qword ptr [rsp+40h] ss:00000000`0012b280=2200000000000000
    0:000> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Exception Analysis                                   *
    *                                                                             *
    *******************************************************************************
    
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for QtCore4.dll - 
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for QtGui4.dll - 
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for directsound_win64.dll - 
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for windowsaudiosession_win64.dll - 
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for appscanner_plugin.dll - 
    
    FAULTING_IP: 
    ts3client_win64!ts3celt_celt_decoder_create+2aa18
    00000001`40698338 488b5c2440      mov     rbx,qword ptr [rsp+40h]
    
    EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 0000000140698338 (ts3client_win64!ts3celt_celt_decoder_create+0x000000000002aa18)
       ExceptionCode: c0000417
      ExceptionFlags: 00000001
    NumberParameters: 0
    
    PROCESS_NAME:  ts3client_win64.exe
    
    ERROR_CODE: (NTSTATUS) 0xc0000417 - An invalid parameter was passed to a C runtime function.
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000417 - An invalid parameter was passed to a C runtime function.
    
    NTGLOBALFLAG:  0
    
    APPLICATION_VERIFIER_FLAGS:  0
    
    APP:  ts3client_win64.exe
    
    FAULTING_THREAD:  0000000000002788
    
    BUGCHECK_STR:  APPLICATION_FAULT_STATUS_INVALID_CRUNTIME_PARAMETER_AFTER_CALL
    
    PRIMARY_PROBLEM_CLASS:  STATUS_INVALID_CRUNTIME_PARAMETER_AFTER_CALL
    
    DEFAULT_BUCKET_ID:  STATUS_INVALID_CRUNTIME_PARAMETER_AFTER_CALL
    
    LAST_CONTROL_TRANSFER:  from 00000001406a13c1 to 0000000140698338
    
    STACK_TEXT:  
    00000000`0012b240 00000001`406a13c1 : 00000000`00000022 00000000`05111c30 ffffffff`ffffffff 00000000`00000004 : ts3client_win64!ts3celt_celt_decoder_create+0x2aa18
    00000000`0012b280 00000001`40200fdb : 00000000`00000000 00000000`00000005 00000000`020d6d40 ffffffff`ffffffff : ts3client_win64!ts3celt_celt_decoder_create+0x33aa1
    00000000`0012b2c0 00000001`40330b17 : 00000000`020d09d0 00000000`00000001 00000000`00000000 00000000`04691380 : ts3client_win64!opus_repacketizer_out+0x1f037b
    00000000`0012b6b0 00000001`4035e9af : 00000000`00000000 00000000`00000000 00000000`028c6960 00000000`00000000 : ts3client_win64!opus_repacketizer_out+0x31feb7
    00000000`0012b960 00000000`6617ce1e : 00000000`020c9860 00000001`4035d1f0 00000000`045e2d40 00000000`0012bb60 : ts3client_win64!opus_repacketizer_out+0x34dd4f
    00000000`0012bb30 00000000`66182291 : 00000000`046912e0 00000000`029bb290 3ff00000`00000004 00000000`046912e0 : QtCore4!QMetaObject::activate+0x57e
    00000000`0012bbf0 00000000`6617abc8 : 00000000`028ddc80 00000000`028ddc80 00000000`00000000 00000015`00000000 : QtCore4!QTimer::timerEvent+0xd1
    00000000`0012bc20 00000000`65650262 : 00000000`0012f868 00000000`01cdb360 00000000`046912e0 00000000`0012c158 : QtCore4!QObject::event+0x58
    00000000`0012be10 00000000`6565180f : 00000000`00000022 00000000`0012f868 00000000`0012c100 00000000`0012c158 : QtGui4!QApplicationPrivate::notify_helper+0x102
    00000000`0012be40 00000000`66167aa4 : 00000000`01cdc600 00000000`01cd4aa0 00000000`00000000 00000000`00000002 : QtGui4!QApplication::notify+0x23f
    00000000`0012c0e0 00000000`6618f64e : 00000000`01cdc6a0 00000000`002d0200 00000000`002d0264 00000000`045e2d40 : QtCore4!QCoreApplication::notifyInternal+0x74
    00000000`0012c130 00000000`6618fdc2 : 00000000`1b00000a 00000000`00000113 00000000`00000000 00000000`00000000 : QtCore4!QEventDispatcherWin32::interrupt+0x5be
    00000000`0012c190 00000000`76ac9bd1 : 00000000`00000000 00000000`00000000 00000000`0000fffd 00000339`00000004 : QtCore4!QEventDispatcherWin32::event+0x5e2
    00000000`0012c240 00000000`76ac98da : 00000000`0012c3b0 00000000`6618fbe0 00000000`0012f768 00000000`008ad950 : user32!UserCallWinProcCheckWow+0x1ad
    00000000`0012c300 00000000`6619238a : 00000000`01ccecb0 00000000`01ccecb0 00000000`6618fbe0 00000000`00000001 : user32!DispatchMessageWorker+0x3b5
    00000000`0012c380 00000000`656b0d25 : 00000000`01ccecb0 00000000`0012f768 00000000`04464400 00000000`0012f868 : QtCore4!QEventDispatcherWin32::processEvents+0x92a
    00000000`0012f730 00000000`66166c28 : 00000000`01cd4ae8 00000000`00000024 ffffffff`00000002 00000000`01cd4ae9 : QtGui4!QApplicationPrivate::translateTouchEvent+0x8a5
    00000000`0012f760 00000000`6616b800 : 00000000`00000024 00000000`01cd4aa0 00000000`00000024 00000000`01ce4448 : QtCore4!QEventLoop::exec+0x278
    00000000`0012f7d0 00000001`403b42ae : 00000000`00000000 00000000`ffffffff 00000000`ffffffff 00000000`043c8628 : QtCore4!QCoreApplication::exec+0xe0
    00000000`0012f820 00000001`406a288d : 00000000`00000000 00000000`00000000 00000001`40000000 00000001`40000000 : ts3client_win64!opus_repacketizer_out+0x3a364e
    00000000`0012feb0 00000000`76e7652d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ts3client_win64!ts3celt_celt_decoder_create+0x34f6d
    00000000`0012ff60 00000000`771bc521 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0xd
    00000000`0012ff90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d
    
    
    STACK_COMMAND:  ~0s; .ecxr ; kb
    
    FOLLOWUP_IP: 
    ts3client_win64!ts3celt_celt_decoder_create+2aa18
    00000001`40698338 488b5c2440      mov     rbx,qword ptr [rsp+40h]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  ts3client_win64!ts3celt_celt_decoder_create+2aa18
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: ts3client_win64
    
    IMAGE_NAME:  ts3client_win64.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  50c1ba3a
    
    FAILURE_BUCKET_ID:  STATUS_INVALID_CRUNTIME_PARAMETER_AFTER_CALL_c0000417_ts3client_win64.exe!ts3celt_celt_decoder_create
    
    BUCKET_ID:  X64_APPLICATION_FAULT_STATUS_INVALID_CRUNTIME_PARAMETER_AFTER_CALL_ts3client_win64!ts3celt_celt_decoder_create+2aa18
    
    WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/ts3client_win64_exe/3_0_10_0/50c1ba3a/ts3client_win64_exe/3_0_10_0/50c1ba3a/c0000417/00698338.htm?Retriage=1
    
    Followup: MachineOwner
    ---------

    I know, next up is I'm getting told that "this is unusable" for some reason, to which my question remains:

    If it is, as you imply, TS3 that generates the CrashDumps, then why am I getting my CrashDumps put into C:\Users\Username\AppData\Local\CrashDumps instead of C:\Users\Username\Documents?
    Maybe someone should look into that, if all my research is for nought.
    Attached Files Attached Files

  11. #26
    Join Date
    July 2010
    Location
    Germany
    Posts
    27
    New build (1357824174), same crash.
    Dumps, WinDbg output and client logs attached.

    Should I make a separate thread about the crash dumps not being generated in the way you prefer?
    Attached Files Attached Files

  12. #27
    Join Date
    September 2012
    Posts
    6,076
    Your crashdumps being created in %LocalAppData%\CrashDumps might very well be caused by the fact that you have WinDbg installed and/or specified it as global debugger in windows.
    Uninstalling it completely might fix that and make it so that TeamSpeak creates the dump files in the proper place.

  13. #28
    Join Date
    July 2010
    Location
    Germany
    Posts
    27
    Thanks, I'll give that a try as soon as possible!

  14. #29
    Join Date
    July 2010
    Location
    Germany
    Posts
    27
    Revisting this, since 3.0.10 is out now:

    I tried removing WinDbg, I even tried it all in both a cleanly installed Windows 7 and Windows 8 VM, the problem always persisted.

    After talking to many users of my server, I'm pretty sure it must be related to it. We've had several new users join us who've never before experienced this problem, but after joining our server, they now have.
    Also, none of these people get crash dumps (neither where you want them, nor where they go for me). And they don't have any debuggers installed, let alone know what WinDbg is.


    I made some suggestions and reported on what happens pretty thoroughly, but nobody has commented on all that info, yet.
    Could someone spare a minute or 5 to read my detailed posts?
    The main points that went without any reply were:
    • settings.db
    • ts3_celt_decoder_create being the last instruction pointer in all cases


    Also, if it helps, I'd invite you to my server. You could just idle on there until this problem occurs.
    Alternatively, is there any way you could get me a debug build without symbols stripped away?
    That should result in a more detailed crash dump, should it not?


    I'm pretty much out of ideas otherwise.


    P.S.: I upgraded our server to 3.0.7, which of course forces clients to update to 3.0.10, and on my first connect it crashed. Great. Time to downgrade and be stuck in the past.

  15. #30
    Join Date
    September 2012
    Posts
    6,076
    If you have a crashdump from the 3.0.10 client version (regardless whether created by WinDbg, Windows or the client itself) please provide that too.

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. Replies: 0
    Last Post: August 4th, 2013, 01:52 PM
  2. [Resolved] client does not log tsdns srv record connection fails
    By Elradon in forum Bug Reports [EN/DE]
    Replies: 6
    Last Post: September 7th, 2012, 11:04 AM
  3. [Resolved] Problems with 32bit client and TSDNS
    By CrazyRuben in forum Windows
    Replies: 3
    Last Post: October 7th, 2011, 11:36 PM
  4. Replies: 1
    Last Post: September 12th, 2011, 11:34 AM
  5. Replies: 3
    Last Post: July 18th, 2011, 04:00 PM

Posting Permissions

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