Report #3544
Some units getting _psyche crash loops when repair messages are consistently sent via public bus
| source | armelthelae |
|---|---|
| version | 0.5.1 |
| status | IDK |
| priority | TRI |
| target fix | 0.5.4 |
| report date | 2025-05-28 14:48:49 |
| report | Two units (SL account names clairebear and jessicathunderstone) have reported crashes when utilizing a third-party option that charges and repairs. Upon attempting to assist with troubleshooting I could not replicate this behavior on myself, but could repeatedly do so to Claire. Upon further testing, I created a box that sends a "repair 20" message once per second over the public bus that consistently resulted in the same crash loops after it had been running for 10-20 seconds for these units, but did not cause the same issue with my own system. I made sure NO external items that could be communicating with Claire's system at the time, and she has a fully up-to-date ARES installation. The only additional module she has installed is TESI 0.9.2, which should be the same version I have installed, and isn't likely to be a contributing factor. Filing this report just in case this might be on the ARES side, since I'm unsure why this would be happening to her system and not mine from the same sources with essentially the same setups. |
a year ago
armelthelae:
As this appears to have come up again, further testing notes: ANY wireless repair messages received at an interval of at least 5 seconds apart or faster tends to cause these psyche stack-heaps on units that have Sexuality installed. 10 seconds seems to be a safe number, from my own testing, so the "safe" threshold is likely somewhere between these two, but unsure why this happens specifically with wireless repair messages and not, say, wireless charging.