[Client Issue] Client crashed soon after joining (local) Server


  • crash.dmp

    KERNELBASE.dll caused a Breakpoint (0x80000003)
    in module KERNELBASE.dll at 0033:d7780262.

    Error occurred at 2015-11-26_230146.
    E:\Games\ECO\Eco.exe, run by David.
    65% memory in use.
    8128 MB physical memory [2844 MB free].
    16320 MB paging file [9386 MB free].
    134217728 MB user address space [134216133 MB free].

    Initialize engine version: 5.2.2f1 (3757309da7e7)
    GfxDevice: creating device client; threaded=1
    Direct3D:
    Version: Direct3D 11.0 [level 11.0]
    Renderer: NVIDIA GeForce GTX 960 (ID=0x1401)
    VRAM: 1969 MB

    ========== OUTPUTING STACK TRACE ==================

    0x00007FFCAE73676D (mono) unity_mono_method_is_generic
    RtlLookupFunctionEntry returned NULL function. Aborting stack walk.
    ========== END OF STACKTRACE ===========

    **** Crash! ****


    No Idea how, but when I FIRST joined my local Server hosted on the same PC as the client, I soon after had a client crash.
    Server was just fine.. no issue with that.

    Reproduce-able? Not yet happened again.
    Windows10
    first Alpha release client and server.

    Hope I got it all right.

    Greetings,
    Dave

    ~ Dev. Tier Backer ~


  • 4
    Posts
    1790
    Views
    Log in to reply


  • this has only happent once randomly ?



  • Well since that was my first time on my own server...

    So I started it up again today and logged on and off for 5 Times or so.
    But I could not reproduce it.

    Maybe it was an initial "fresh" server issue where the client just went online too soon?

    Sry for the vague details.. I have no more than that I'm afraid..

    Btw, if it isn't reported yet: If you log off on Coord X/Y/Z (Y being hight) and relog, you start off at X/Y+2/Z (or +3..)
    Can be reproduced since it happens all the time.

    ~ Dev. Tier Backer ~



  • maybe .. strange it happens on kernelbase to ...


4
Posts
1790
Views
Log in to reply

Internal error.

Oops! Looks like something went wrong!