We’ve been looking into some issues with the software update framework that RapidWeaver uses, where updates wouldn’t necessarily be applied, and where when reporting a crash the problem reporter would start to consume a substantial amount of memory. These are items related to some third-party components we use, and I’ve been working with DevMate (the service we use) to get these investigated!
While there will likely be some more fixes in RapidWeaver 6.3.7, I wanted to get a beta out with this new update checking system so that anyone experiencing those issues can test and report back about the changes. If you have been experiencing problem reporter issues, please let me know how you get on!
Changes in RapidWeaver 6.3.7
- RapidWeaver is now using the very latest version of the problem reporter and software update systems from DevMate.
If you’re happy with the risks associated with using pre-release software you can download the latest beta here.