Crash in bambu_networking.dll (+0xD5447A) on startup and on send-to-printer — P1S, 2.8.2.60

### Bambu Studio Version 2.8.2.60 ### Where is the application from? Bambu Lab Official website ### OS version Windows 10.0.28000 (x64) ### Additional system information 32 logical CPUs. Printer is on the local network; LAN Only + Developer mode enabled. ### Printer P1S ### How to reproduce 1. Launch Bambu Studio — crashes during startup. 2. Rename `%APPDATA%\BambuStudio\plugins` so the network plugin is absent — Studio now launches normally. 3. Reinstall the Network Plugin from within Studio. 4. Slice any model and press **Print plate / Send to printer** — Studio crashes again. ### Actual results Crash. Eleven crash dumps were collected across both failure points (startup before the plugin was removed, and send-to-printer after reinstalling it). **All eleven fault at the same instruction inside `bambu_networking.dll`:** ``` Exception : 0xC0000005 ACCESS_VIOLATION (invalid read) Module : bambu_networking.dll Offset : +0xD5447A <-- identical in every dump ``` The absolute address differs between dumps only by the ASLR load base; the module-relative offset is constant, so this is one code path rather than several. The address being read belongs to **no loaded module** in any of the dumps — it is not a null dereference but a stale or uninitialised pointer. Example from one dump: ``` fault address 0x00007FF8A841447A module base 0x00007FF8A76C0000 (size 0x2A74000) offset +0xD5447A read target 0x00007FF8933ADFD8 -> not within any loaded module ``` The faulting DLL is not part of the Studio installation — it is the separately downloaded network plugin at `C:\Users\<user>\AppData\Roaming\BambuStudio\plugins\bambu_networking.dll`. **Reinstalling the plugin does not help:** the redownloaded binary faults at the same offset, which suggests the same build is served rather than the local copy being corrupt. Strings present in the dump heap (`bambulab.com`, `cloud`, `access_code`, `sequence_id`, the printer serial) suggest the cloud send path, though I could not confirm that without symbols. ### Expected results Studio launches with the network plugin present, and sending a sliced plate to the printer starts the print. ### Project file & Debug log uploads Crash dumps can be provided on request — they are ~40–50 MB each, so I have not attached them. Happy to upload a specific one, or run any additional diagnostics that would help. ### Anything else? Stack frames are not included because I do not have symbols for `bambu_networking.dll`; the offset above should be resolvable internally. **A different version of the same plugin works on this machine.** I am currently printing to the same P1S over LAN from OrcaSlicer, which loads `bambu_networking.dll` as well — it requires it to talk to the printer. Its plugin is set to **`02.03.00.62`**. Same PC, same printer, same DLL, no crash. That suggests the build Studio is using is a regression rather than something specific to this machine or network. Studio's copy of the DLL carries no version resource (it reports `0.0.0.0`), so I cannot say which build it is — but comparing it against `02.03.00.62` looks like the fastest route to the fix.