Support Board
Date/Time: Wed, 15 Oct 2025 06:50:14 +0000
Post From: ALWAYS BACK UP CHARTBOOKS WHEN UPDATING / ROLLING BACK - CHARTBOOKS COULD BE DESTROYED
| [2025-10-12 01:16:12] |
| User677437 - Posts: 75 |
|
I'm posting this, because this is DIRE and unnacceptable ! I rolled backed from 2800 to 2771 because that's what a friend was using. When I rolled back and wanted to launch my main chartbook - my ram use went to 99% My charts and SC froze, and when it loaded - it all looks corrupted - I've never seen this before. It's time that the SC team gets a team in place of veteran users that have substantially built out chartbooks to beta test updating and rolling back. We understand that yall are working on new network and accessibility features, but if that's incompatible to the vendors and the chartbook market / discord communities that all trade the same version, all trade the same chartbooks etc. It's seems like the functionality is being lost. Please look at these images. This is no joke with a memory leak like this. I had to force shutdown my computer. |
 2025-10-11 20_55_20-Task Manager.png / V - Attached On 2025-10-12 01:07:28 UTC - Size: 4.93 KB - 32 views 2025-10-11 21_04_49-Greenshot capture form.png / V - Attached On 2025-10-12 01:07:34 UTC - Size: 51.49 KB - 34 views |