• APPCRASH after update to 3.20a

    From Codefenix@VERT/CONCHAOS to All on Sat Jan 28 15:44:53 2023
    Updated to the latest 3.20a today. Windows 10.

    The Synchronet Control Panel went down pretty suddenly. Found this APPCRASH in the event log:


    Faulting application name: sbbsctrl.exe, version: 3.20.0.0, time stamp: 0x00000000
    Faulting module name: SBBS.DLL, version: 0.0.0.0, time stamp: 0x63d51d3a Exception code: 0xc0000005
    Fault offset: 0x00047316
    Faulting process id: 0x1fd4
    Faulting application start time: 0x01d933556947e1dc
    Faulting application path: C:\sbbs\exec\sbbsctrl.exe
    Faulting module path: C:\sbbs\exec\SBBS.DLL
    Report Id: 6efca7ef-e40d-48d2-858f-8bd4ac266caf
    Faulting package full name:
    Faulting package-relative application ID:


    At the time of the crash I was starting to post a message using SlyEdit, and there was another user logged on playing OOII.

    |01<|09co|03d|11e|15|11e|03n|09ix|01>|07

    ---
    Synchronet -=[ ConstructiveChaos BBS | conchaos.synchro.net ]=-
  • From Digital Man@VERT to Codefenix on Sat Jan 28 15:31:21 2023
    Re: APPCRASH after update to 3.20a
    By: Codefenix to All on Sat Jan 28 2023 03:44 pm

    Updated to the latest 3.20a today. Windows 10.

    The Synchronet Control Panel went down pretty suddenly. Found this APPCRASH in the event log:


    Faulting application name: sbbsctrl.exe, version: 3.20.0.0, time stamp: 0x00000000
    Faulting module name: SBBS.DLL, version: 0.0.0.0, time stamp: 0x63d51d3a Exception code: 0xc0000005
    Fault offset: 0x00047316
    Faulting process id: 0x1fd4
    Faulting application start time: 0x01d933556947e1dc
    Faulting application path: C:\sbbs\exec\sbbsctrl.exe
    Faulting module path: C:\sbbs\exec\SBBS.DLL
    Report Id: 6efca7ef-e40d-48d2-858f-8bd4ac266caf
    Faulting package full name:
    Faulting package-relative application ID:


    At the time of the crash I was starting to post a message using SlyEdit, and there was another user logged on playing OOII.

    Unfortunately, there's not much I can do with that crash info as
    v3.20a is a moving target, changing every day, which build was this?

    I could maybe correlate that fault offset with a specific line of code, but I'd have to know exactly which build to correlate with that address.

    Do you have MQTT enabled perhaps? There has been a few MQTT related crashing-bugs that have been fixed recently.
    --
    digital man (rob)

    Breaking Bad quote #22:
    I got one more shot at that little skid mark. - Hank Schrader
    Norco, CA WX: 60.7F, 53.0% humidity, 1 mph E wind, 0.00 inches rain/24hrs
    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Codefenix@VERT/CONCHAOS to Digital Man on Sun Jan 29 09:12:47 2023
    Re: APPCRASH after update to 3.20a
    By: Digital Man to Codefenix on Sat Jan 28 2023 03:31 pm

    Unfortunately, there's not much I can do with that crash info as
    v3.20a is a moving target, changing every day, which build was this?

    I used the latest build that was available yesterday. In the "about" screen, it says:

    Compiled master/adb05e50f Jan 28 2023 05:03:16 with MSC 1929

    Does that help?

    Do you have MQTT enabled perhaps? There has been a few MQTT related crashing-bugs that have been fixed recently.

    No. I didn't know what MQTT was until today. :)

    |01<|09co|03d|11e|15|11e|03n|09ix|01>|07

    ---
    Synchronet -=[ ConstructiveChaos BBS | conchaos.synchro.net ]=-
  • From Digital Man@VERT to Codefenix on Sun Jan 29 13:32:49 2023
    Re: APPCRASH after update to 3.20a
    By: Codefenix to Digital Man on Sun Jan 29 2023 09:12 am

    Re: APPCRASH after update to 3.20a
    By: Digital Man to Codefenix on Sat Jan 28 2023 03:31 pm

    Unfortunately, there's not much I can do with that crash info as
    v3.20a is a moving target, changing every day, which build was this?

    I used the latest build that was available yesterday. In the "about" screen, it says:

    Compiled master/adb05e50f Jan 28 2023 05:03:16 with MSC 1929

    Does that help?

    Perhaps. For recent builds, that offset appears to correlate with a function in js_client.c:

    0001:00047300 _js_client_resolve 10048300 f js_client.obj

    but I don't see anything obviously wrong with that function or a reason why it would crash there; that part of the code hasn't changed in a long while.

    I'm going to reproduce a build with that exact Git-SHA and see if that still correlates to that function.

    If you have a known-method of reproducing the crash, that could be very helpful!

    Do you have MQTT enabled perhaps? There has been a few MQTT related crashing-bugs that have been fixed recently.

    No. I didn't know what MQTT was until today. :)

    MQTT support a new experimental feature still, but just good to know that it's not part of the equation of your problem.
    --
    digital man (rob)

    Breaking Bad quote #38:
    Don't drink and drive, but when you do, call Saul.
    Norco, CA WX: 54.5F, 72.0% humidity, 6 mph E wind, 0.00 inches rain/24hrs
    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Digital Man@VERT to Codefenix on Sun Jan 29 14:15:40 2023
    Re: APPCRASH after update to 3.20a
    By: Digital Man to Codefenix on Sun Jan 29 2023 01:32 pm

    I'm going to reproduce a build with that exact Git-SHA and see if that still correlates to that function.

    In a build that correlates with the Git-SHA of the build you're using, that Fault address correlates with js_client_get, a different function in that same source file (js_client.c). No more clues at this point.
    --
    digital man (rob)

    Sling Blade quote #15:
    Doyle Hargraves: What'cha doin' with that lawn mower blade Karl?
    Norco, CA WX: 52.7F, 78.0% humidity, 4 mph SSW wind, 0.00 inches rain/24hrs ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Codefenix@VERT/CONCHAOS to Digital Man on Sun Jan 29 19:35:00 2023
    Re: APPCRASH after update to 3.20a
    By: Digital Man to Codefenix on Sun Jan 29 2023 01:32 pm

    If you have a known-method of reproducing the crash, that could be very helpful!

    It hasn't happened since that one time. I'll be sure to report back if it happens again though.

    |01<|09co|03d|11e|15|11e|03n|09ix|01>|07

    ---
    Synchronet -=[ ConstructiveChaos BBS | conchaos.synchro.net ]=-