TZUTC: -0800   
   MSGID: 57127.sync_sys@1:103/705 2bda9c9d   
   REPLY: 57125.sync_sys@1:103/705 2bd9f78b   
   PID: Synchronet 3.20a-macOS master/993d7bac8 Dec 28 2024 Clang 16.0.0   
   TID: SBBSecho 3.23-Linux master/7c2ca73d2 Dec 29 2024 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.105   
     Re: hanging my bbs   
     By: Max to Digital Man on Tue Dec 31 2024 01:23 pm   
      
    >   Re: hanging my bbs   
    >   By: Digital Man to Max on M†n Dec 30 2024 18:16:54   
    >   
    >  DM> I noticed your JS runtime heap size is a bit small at 16M. The default   
    >  DM> nowadays is 10x that (160M). Just as an experiment, you want to try   
    >  DM> increasing that value (e.g. in   
    >  DM> SBBSCTRL:File->properties->JavaScript->Heap Size)?   
    >   
    > I has change it to 160M now.   
    >   
    >  DM> I do think it's interesting that you're getting a debug assertion,   
    >  DM> which I think can only happen in debug builds (e.g. of websrvr.dll).   
    >  DM> Are you building your own Synchronet executables? If you are, that   
    >  DM> implies you'd have MSVS/C++ installed and could potentially attach its   
    >  DM> debugger to the crashed sbbs and get a backtrace (callstack). That   
    >  DM> could be very useful in helping to root-cause and resolve this heap   
    >  DM> corruption.   
    >   
    > Yes, i build it myself with MS Visual Studio 2022, and it is debug build,   
    > but I cant mush about debugging...   
      
   Why not? That would be *really* helpful for root-causing and resolving the   
   problem:   
   https://wiki.synchro.net/howto:msvc   
      
   You often can just attach the process (sbbsctrl.exe) with the debugger (MSVS)   
   at the time of the crash and copy the backtrace/callstack.   
      
    >  DM> Another thing that could potentially help would be a packet ure (e.g.   
    >  DM> using Wireshark), so we could maybe feed that same HTTP POST request   
    >  DM> back into a webserver and reproduce the crash.   
    >   
    > will try that.   
    >   
    > All you have done didn't help, he is back again. And the error windows still   
    > popup.   
    > Lastest log at https://pepzi.net/hang2.txt   
    > Thanks anyway   
      
   Does it happen if you use the (release) binaries from sbbs_dev.zip instead?   
   I'm not clear why you're building debug binaries yourself if you can't (or   
   won't) help debug it.   
   --    
                                               digital man (rob)   
      
   Rush quote #24:   
   The more that things change, the more they stay the same   
   Norco, CA WX: 60.8øF, 68.0% humidity, 2 mph WNW wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.23-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 10/0 1 102/401 103/1 13 17 705 105/81 106/201 124/5016 128/187   
   SEEN-BY: 153/7715 214/22 218/0 1 215 601 700 720 840 860 880 226/30   
   SEEN-BY: 227/114 229/110 114 206 317 400 426 428 470 550 700 705 266/512   
   SEEN-BY: 280/464 282/1038 291/111 301/1 320/219 322/757 342/200 396/45   
   SEEN-BY: 460/58 633/280 712/848 902/26 5075/35   
   PATH: 103/705 218/700 229/426