# Classic crashing all day long **URL:** \ **Category:** RapidWeaver Classic\ **Created:** [May 20, 2025, 9:21pm UTC](https://forums.realmacsoftware.com/t/classic-crashing-all-day-long/47676 "2025-05-20T21:21:01Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![papart](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/papart/32/20089_2.png) [@papart](https://forums.realmacsoftware.com/u/papart)\ **Post date:** [May 20, 2025, 9:21pm UTC](https://forums.realmacsoftware.com/t/classic-crashing-all-day-long/47676/1 "2025-05-20T21:21:01Z")
I recently updated Version 8 to classic and have both versions on my Mac. Mac OS 15.4.1, Mac Studio M1. I have been dealing with many crashes over the past few days and I wonder if there are any library files I can delete in order to get classic on track? RW 8 was slow (that was the reason I updated to classic), but it worked. With classic I have spent hours re-doing work which was ruined, because I missed to save the document more often. I learned my lesson now and save literally after ever little edit - but this is not what I expected from the update. Any help very much appreciated, because I have to finish a homepage asap. ---
**Author:** ![Heroic\_Nonsense](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/heroic_nonsense/32/20666_2.png) [@Heroic\_Nonsense](https://forums.realmacsoftware.com/u/Heroic_Nonsense)\ **Post date:** [May 21, 2025, 6:54am UTC](https://forums.realmacsoftware.com/t/classic-crashing-all-day-long/47676/2 "2025-05-21T06:54:02Z")
Hi @papart, Instead of deleting files willy-nilly, it’s best to first investigate _why_ this is happening. macOS will display a crash report after it has done handling the crash. Could you post that here? Cheers, Erwin ---
**Author:** ![papart](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/papart/32/20089_2.png) [@papart](https://forums.realmacsoftware.com/u/papart)\ **Post date:** [May 21, 2025, 2:59pm UTC](https://forums.realmacsoftware.com/t/classic-crashing-all-day-long/47676/3 "2025-05-21T14:59:26Z")
I was presented this silly message several times and can not get my head around what might be the reason for this? I mean: I have 1 document opened in classic – which _other_ application could that be, which “modified” my document??? It´s not the only kind of crash I experience, but after this message I have to “force quit” RW in order to get rid of the never-ending beachball. ![CleanShot 2025-05-21 at 16.55.30@2x](https://europe1.discourse-cdn.com/flex005/uploads/realmacsoftware1/original/3X/4/4/44135a23376b28e6315d7ad1f5ba2586a7158aad.jpeg) ---
**Author:** ![papart](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/papart/32/20089_2.png) [@papart](https://forums.realmacsoftware.com/u/papart)\ **Post date:** [May 21, 2025, 3:02pm UTC](https://forums.realmacsoftware.com/t/classic-crashing-all-day-long/47676/4 "2025-05-21T15:02:30Z")
I don´t know if it’s a good idea to paste in the crash report which was presented after quitting in order to send it to apple…? It´s a pretty long text…?! ---
**Author:** ![Heroic\_Nonsense](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/heroic_nonsense/32/20666_2.png) [@Heroic\_Nonsense](https://forums.realmacsoftware.com/u/Heroic_Nonsense)\ **Post date:** [May 22, 2025, 12:09pm UTC](https://forums.realmacsoftware.com/t/classic-crashing-all-day-long/47676/5 "2025-05-22T12:09:05Z")
Hi @papart, In order to figure out _why_ RapidWeave crashes, you actually do need that very long report. Cheers, Erwin ---
**Author:** ![tpbradley](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/tpbradley/32/25503_2.png) [@tpbradley](https://forums.realmacsoftware.com/u/tpbradley)\ **Post date:** [May 22, 2025, 4:15pm UTC](https://forums.realmacsoftware.com/t/classic-crashing-all-day-long/47676/6 "2025-05-22T16:15:00Z")
Hi @papart, Erwin is right, we could really do with the crash report to know what’s going on. However, we should be able to narrow it down a little if you feel comfortable doing so. Open the crash report in a text editor and you should see something similar to the following line near the top of the file, it may have a different number. ```auto Crashed Thread: 9 ``` This means thread 9 is the issue and we need to see what it was doing. All the threads are listed next in numerical order. Scroll down until you reach the thread that crashed, in my case it would look like this ```auto Thread 9 Crashed: ``` It’s the information in this section which is important, and it’s generally not too long. Just copy and paste it here. Cheers Tom