dbkw64_24_0.exe that uses 100% CPU time

-
dbkw64_24_0.exe that uses 100% CPU time

Does anyone have same problems ?

Look at https://quality.embarcadero.com/browse/RSP-16915

We can't work in this conditions.

Migrate our software on win64 before Linux, it's the priority !

I hope that Embarcadero don't forget its historical clients.
https://quality.embarcadero.com/browse/RSP-16915

Comments

  1. Stefan GlienkeMarch 23, 2017 at 4:08 PM

    While the issue is bad (I also had that before) there is not much QA can do with the information you provide I am afraid.
    Open a support ticket with them and try to provide more information or even give them access to your environment so they can look into it.

    ReplyDelete
  2. Laurent ESPARIATMarch 24, 2017 at 8:54 AM

    test with Tokyo in same conditions -> It's worse.

    Launch a win32 debug session for a huge project -> unusable with Tokyo (almost 3 minutes to launch the executable - a few seconds with Berlin).

    I am very worried.

    Does Andreas Hausladen can save us again ?

    ReplyDelete
  3. Laurent ESPARIATMarch 25, 2017 at 10:57 AM

    more info acquire with windbg

    A lot of exception INVALID_HANDLE in a thread of dbkw64_24_0.exe.
    I have this exception even on a HelloWord application

    When the CPU usage is high, callstack of main thread (dbkw64_24_0.exe) is something like this.

    Call Site
    dcc64240n!CallNextUnitFreeHookEx+0x3d15
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0x3d6b
    dcc64240n!CallNextUnitFreeHookEx+0x3dc2
    dcc64240n!CallNextUnitFreeHookEx+0xa0
    dcc64240n!CallNextUnitFreeHookEx+0x2fa
    dcc64240n!ClearCompState+0xdd
    dcc64240n!ClearCompState+0x13
    dcc64240n!GetFileIndex+0x159a
    dcc64240n!DbEval32InitProc+0x32e
    dbkw64_24_0_6c940000+0xafc5
    dbkw64_24_0_6c940000+0x62e7
    dbkw64_24_0_6c940000+0x27c00
    dbkw64_24_0_6c940000+0x301c3
    dbkw64_24_0_6c940000+0x1d495
    dbkw64_24_0_6c940000+0x1fd4c
    dbkw64_24_0_6c940000!libStart+0x1b6
    dbkw64_24_0_6c940000!libStart+0xc69
    USER32!UserCallWinProcCheckWow+0x1ad
    USER32!DispatchMessageWorker+0x3b5
    dbkw64_24_0!setLogFileH+0xcdfe
    dbkw64_24_0!setLogFileH+0x5ffe
    dbkw64_24_0!setLogFileH+0x61b5
    USER32!UserCallWinProcCheckWow+0x1ad
    USER32!DispatchMessageWorker+0x3b5
    dbkw64_24_0!setLogFileH+0xcb46
    dbkw64_24_0!setLogFileH+0x49a4
    dbkw64_24_0+0x182f
    dbkw64_24_0+0x13b5
    dbkw64_24_0+0x14e8
    kernel32!BaseThreadInitThunk+0xd
    ntdll!RtlUserThreadStart+0x1d

    Any idea ?

    ReplyDelete

Post a Comment