Property 0b crash

  • bomb_creator
    28th July Member 0 Permalink

    I type 0b in the ctype of anything, boom. "Unrecoverable fault" blue screen instantly. It happened randomly; I tried reproducing (control P, ctype, put 0b) but it didn't cause the unrecoverable fault.


    Crash log:

    ERROR - Details: unhandled exception not derived from std::exception, cannot determine reason
    An unrecoverable fault has occurred, please report it by visiting the website below

    https://powdertoy.co.uk

    An attempt will be made to save all of this information to crash.log in your data folder.
    Please attach this file to your report.

    Version: 100.0.399 X86_64-DARWIN-MACOS LUACONSOLE HTTPS
    Tag: v100.0.399
    Date: 2026-07-28T19:29:45Z
    Stack trace; Main is at 0x104ebeba0:
    - 0 powder 0x0000000105060b9e _ZN8Platform10StackTraceEv + 46
    - 1 libc++abi.dylib 0x00007ff81211e017 __cxa_get_exception_ptr + 0
    - 2 libc++abi.dylib 0x00007ff81210cdbc __cxa_get_globals + 0
    - 3 libc++.1.dylib 0x00007ff8120a5a6f _ZNSt3__124__throw_invalid_argumentB9nqe210106EPKc + 56
    - 4 libc++.1.dylib 0x00007ff8120a5a13 _ZNSt3__112_GLOBAL__N_129throw_from_string_invalid_argERKNS_12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEE + 51
    - 5 libc++.1.dylib 0x00007ff81208688c _ZNSt3__14stoiERKNS_12basic_stringIcNS_11char_traitsIcEENS_9allocatorIcEEEEPmi + 199
    - 6 powder 0x00000001050400d3 _ZN14AccessProperty5ParseEi6String + 1171

     

     

    Edit: Resolved. Please lock this thread.

    Edited 6 times by bomb_creator. Last: 29th July
  • jacob1
    29th July Developer 0 Permalink
    That's weird ... for the new binary mode, it uses std::stoi/std::stol. Those do throw exceptions but they are handled in a catch block below so shouldn't cause this error. It's throwing std::invalid_argument because 0b is invalid binary.

    Does it happen every time when you follow the steps you gave? For me it's not happening.
    - Ctrl/Cmd + P
    - Press down twice to switch to ctype
    - Type 0b
  • LBPHacker
    29th July Developer 0 Permalink
    This bug has been confirmed (only on macos...) and fixed, thanks for reporting it.