I tried your file with my settings and all went well. By process of elimination I found that the issue is a specific file in my project.
Thanks for the help:)
1 Like
I jinxed us. Iām sorry. After making lots of edits to my project to incorporate alpha feedback, I selected the entire manuscript to do some searches and it tried to load all the chapter folders, and after it went on for about two seconds (longer than normal) it crashed. Are you able to share what condition(s) your fixes are trying to mitigate? Maybe that would help me determine if I am inadvertently creating those conditions during the course of my content creation.
Hereās the crash report.
Update:
I then loaded the project backā¦and was able to pull the entire manuscript into memory at the same time. Tried that twice, and it worked both times after the crash that generated the report above. It seems almost as if there may be something related to lots of changes happening just before trying to pull the entire project into the editor.
Just my two cents, and very low priority. I like having the option of system-wide inline predictive text remaining on, but having the option of Scrivener turning them off within the appā¦assuming thatās even possible.
Argh. On the very slightly positive note, that crash log is a little different from the othersā¦ but close enough to have me worried. Certainly not great news for 10pm on a Friday night!
Iād be very grateful if you can keep trying to find a reliable reproduction case. What I found when testing the issue was that even resizing the binder to change the width of the editor could change whether it was reproducible. Also clicking into one page and then into another would do it.
Thanks and all the best,
Keith
P.S. On what the fix does, itās a little technical. Essentially each page contains a text view, and each text view is really a wrapper around a rectangular ātext containerā which handles the layout (these are all part of Appleās TextKit).
These pages (text views/containers) should be of a fixed size. However, what I discovered is that when you click into a page with the new Sonoma text cursor, and when the page is scaled, sometimes the text view can be told to resize (by private methods in Appleās frameworks) to something with a fractional value. So, suppose the rectangle should be 478 x 700. Suddenly itās told to resize to 477.873 x 700.5672. This resizes the text container to those fractional values, and this seemed to be corrupting layout. (Rounding or not rounding can have some very strange effects on the text system - itās all somewhat fragile, it seems.)
My fix just told the containers not to resize if the text view was resized, so that layout shouldnāt be affected by any weird fractional alterations caused by Appleās private voodoo.
None of this is something youāll be able to see, of course. But these weird size changes are happening when you click into a page, as far as I can see - when one page takes the focus after another one previously had it. At least that is what I surmise from testing.
Sure, Iāll keep on it. Beta books are going out next week so Iāll be having plenty of updates.
I edited a post above with a question that might help, but you may not have seen it. What conditions have your previous fixes been designed to mitigate. They clearly have done āsomething,ā because it works much better. Knowing what has made it better might help me understand what Iām doing thatās still causing the problem. ** Just saw your addendumā¦I think I understand **
Also, when you say, clicking into one page and then another. Do you mean, clicking among pages in page view within one chapter folder, and THEN selecting manuscript to have scrivener load them all?
10 pmā¦sorry you are working so late, but very much appreciate you and your whole team. I had no idea yāall were in Europe or somewhere Europe-ish.
We just cross-posted - see my second reply above.
And I just mean that if you have several pages loaded, if you click into say, page 3, and then click into page 2, that was when I was seeing the crash (or layout corruption sometimes).
The team is all over, but Iām in the UK and Iām the one responsible for coding the Mac version. Iām clocking off now and wonāt be working full steam on it again until Monday, but I will keep an eye on this thread over the weekend. I appreciate you taking the time to try out the test builds, try to crash it, and to post here - thank you.
All the best,
Keith
Sounds goodā¦I just made it crash again by clicking among pages then trying to load the full manuscript. Will update this post with a crash report you can āenjoyā on Monday.
Here it is:
Hope you have a good weekend!
Take care,
Robert
Great, thank you. If you can keep repeating the crash, would it be possible to share the project with us (via the support email address)? You can always make a copy of the project, delete everything outside the Draft folder, and then do a project replace on some random letters to make it gibberish and check to see if the crash still happens in the gibberish version if youād rather us not see the text.
Or just the page size youāre using might be a factor too.
Anyway, itās nearly midnight so I really am off - have a great weekend yourself!
All the best,
Keith
Hey Keithā¦hopefully you are asleep 
To your question, I already sent the project to Alex earlier in the week, so you should be able to have access unless heās already destroyed it, which I know is your policy when dealing with an authorās IP.
As for page sizeā¦Iām using 6x9.
Thank you! Okay, thanks to the project you provided, I have managed to reproduce the crash. (Funnily enough, I could only reproduce it by reverting the code to the old text cursor temporarily, but that allowed me to reproduce a crash upon loading the entire text, producing exactly the same crash log as the ones you posted yesterday.)
It seems to be down to a big change in the way views draw in Sonoma - I had suspected this might be a factor.
Prior to Sonoma, a view could only draw inside its own bounds. As of Sonoma, however, views can draw outside of themselves, and when the system asks a view to redraw, it may pass that view a much larger rectangle to draw than it needs - a rectangle outside of itself. (This was the cause of a bug that made it into 3.3.2, where if you turned the ruler on in dark mode, the text in the editor would disappear - because the ruler was drawing outside itself and filling in the editor area with its background colour.)
So, what seems to be happening is this:
- You load some text in the page view, which then lays out. As it lays out, it creates more pages as needed to contain all of the text.
- During layout, some of the text views (each page contains its own text view) may be told to redraw. Drawing may trigger re-layout, but as long as itās contained to the bounds of the text view, it wonāt hurt, because that area has already been laid out properly since itās already inside a page that has been created.
- However, on Sonoma, those text views may be told to redraw an area outside of their bounds. This will then trigger layout in text outside of the page.
- This can result in text that is still in the process of being laid out being sent another layout message, and the page view trying to add a page while itās already in the process of building its pages.
- Crash.
(To clarify, this behaviour only occurs if an app is built on Sonoma and running on Sonoma.)
I have thus updated the code to tell text views inside pages not to allow drawing outside their bounds, which returns them to pre-Sonoma behaviour. Here is a new build with this change (build 16205):
This keeps the previous fix that was mostly working for you too, as I think these may be different bugs. The previous crash was triggered by scaling; I think this crash could occur on long texts even at 100%, given the cause.
Right, I really am going to go and have a weekend now.
All the best,
Keith
P.S. And yes, Iāll delete your project once weāre done reproducing the crashes - fingers crossed this does itā¦
Looks like we are both working the weekend 
First of all, this latest build has made the shift from one chapter folder to all via clicking the manuscript INCREDIBLY fast. There is NO loading wheel. It is almost instantaneous, which incidentally, is what I would have expected from both my M1Max Mac Studio or the M2 MacBook Air. So, whatever you did, is definitely a very good thing from a performance perspective.
Iāll continue to work with this build over the weekend and let you know, if anything nasty crops up.
One questionā¦which Iāll be sorely disappointed if you answer before Monday ā what did you mean by the having been ābuiltā on Sonoma? Do you mean because you literally compiled the Scrivener.app code on a machine running 14.0?
Oh, and if it makes you feel any better, back when I slung code in the dark ages, I rarely could let an annoying bug get the better of me over weekends either. Now thatās translated to home tech. My ļ£æTV has been experiencing insane network jitter, and Iāve been banging my head against it trying to figure what the hell is wrong with my mesh network. Now, I think Iāve isolated it to the actual ļ£æTV being broken itself. If that proves to be the case, how the heck does a wifi chip fail in such a way as to generate additional latency and jitter? Rhetorical. Anywayā¦yeahā¦I should be finalizing my beta books to ship on Mondayā¦butā¦annoying tech issues needs resolving!!!
Sorry to disappoint.
The change that fixes the bug should indeed also speed things up. Part of the problem before was that each individual page could potentially trigger a redraw of every page, and thus relayout of the whole text. So instead of the text being laid out once, it was getting laid out multiple times, possibly even as many times as there were pages - ouch! And this relayout was interfering with ongoing layout passes, leading to occasional crashes. (At least this is what I surmise from debugging.)
Yes, exactly that. Often when Apple makes big changes like this, they will only take effect when an app is recompiled on the new system against the updated frameworks. This guards against older apps breaking and gives the developer time to update the code. In this case, because of this change, when I first compiled Scrivener on macOS 14 before updating the code, every single view was blank - the binder, the editor, the inspector, everything - because everything was drawing over everything else. But 3.3.1 - compiled on Ventura - looked fine.
Good luck with your Apple TV - that doesnāt sound a fun way to spend your Saturday - and with your beta books!
I am having a similar issue using 3.3.3 (15931). Crashes when opening my project.
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------
Process: Scrivener [1257]
Path: /Applications/Scrivener 3.app/Contents/MacOS/Scrivener
Identifier: com.literatureandlatte.scrivener3
Version: 3.3.3 (15931)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2023-10-09 13:18:23.7569 -0400
OS Version: macOS 14.0 (23A344)
Report Version: 12
Bridge OS Version: 8.0 (21P365)
Anonymous UUID: CF4A2612-8FFC-BBEE-B086-3137EBC61789
Time Awake Since Boot: 510 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x000065b97f413b38
Exception Codes: 0x0000000000000001, 0x000065b97f413b38
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [1257]
VM Region Info: 0x65b97f413b38 is not in any region. Bytes after previous region: 6293725199161 Bytes before following region: 11298030777544
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
MALLOC_NANO 600000000000-600020000000 [512.0M] rw-/rwx SM=PRV
---> GAP OF 0xfffe65db000 BYTES
Stack Guard 7000065db000-7000065dc000 [ 4K] ---/rwx SM=NUL
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x7ff8019a191d objc_msgSend + 29
1 UIFoundation 0x7ff8068474f5 -[NSLayoutManager(NSPrivate) _glyphRangeForBoundingRect:inTextContainer:fast:okToFillHoles:] + 891
2 AppKit 0x7ff805554768 -[NSTextView setNeedsDisplayInRect:avoidAdditionalLayout:] + 909
3 ScrAppKit 0x10dedefb2 -[KBBaseTextView setNeedsDisplayInRect:avoidAdditionalLayout:] + 159
4 Scrivener 0x10c92044d 0x10c701000 + 2225229
5 AppKit 0x7ff8054681c6 -[NSView setNeedsDisplay:] + 125
6 AppKit 0x7ff805468090 -[NSView _updateLayerBackedness] + 799
7 AppKit 0x7ff80602a45f -[NSView _buildLayerTreeWithOwnLayerRequirement:someAncestorWantsLayer:singleLayerOut:layerArrayOut:] + 1848
8 AppKit 0x7ff80602a0f7 -[NSView _buildLayerTreeWithOwnLayerRequirement:someAncestorWantsLayer:singleLayerOut:layerArrayOut:] + 976
9 AppKit 0x7ff80602a0f7 -[NSView _buildLayerTreeWithOwnLayerRequirement:someAncestorWantsLayer:singleLayerOut:layerArrayOut:] + 976
10 AppKit 0x7ff80602a0f7 -[NSView _buildLayerTreeWithOwnLayerRequirement:someAncestorWantsLayer:singleLayerOut:layerArrayOut:] + 976
11 AppKit 0x7ff80602a0f7 -[NSView _buildLayerTreeWithOwnLayerRequirement:someAncestorWantsLayer:singleLayerOut:layerArrayOut:] + 976
12 AppKit 0x7ff80602a0f7 -[NSView _buildLayerTreeWithOwnLayerRequirement:someAncestorWantsLayer:singleLayerOut:layerArrayOut:] + 976
13 AppKit 0x7ff80602a0f7 -[NSView _buildLayerTreeWithOwnLayerRequirement:someAncestorWantsLayer:singleLayerOut:layerArrayOut:] + 976
14 AppKit 0x7ff80602a0f7 -[NSView _buildLayerTreeWithOwnLayerRequirement:someAncestorWantsLayer:singleLayerOut:layerArrayOut:] + 976
15 AppKit 0x7ff80602a0f7 -[NSView _buildLayerTreeWithOwnLayerRequirement:someAncestorWantsLayer:singleLayerOut:layerArrayOut:] + 976
16 AppKit 0x7ff80602a0f7 -[NSView _buildLayerTreeWithOwnLayerRequirement:someAncestorWantsLayer:singleLayerOut:layerArrayOut:] + 976
17 AppKit 0x7ff80602a0f7 -[NSView _buildLayerTreeWithOwnLayerRequirement:someAncestorWantsLayer:singleLayerOut:layerArrayOut:] + 976
18 AppKit 0x7ff80602a0f7 -[NSView _buildLayerTreeWithOwnLayerRequirement:someAncestorWantsLayer:singleLayerOut:layerArrayOut:] + 976
19 AppKit 0x7ff80602a0f7 -[NSView _buildLayerTreeWithOwnLayerRequirement:someAncestorWantsLayer:singleLayerOut:layerArrayOut:] + 976
20 AppKit 0x7ff806029cdf -[NSView _buildLayerTree] + 522
21 AppKit 0x7ff80550e2ef NSViewBuildLayerTreeForDisplay + 32
22 AppKit 0x7ff80603dd8c NSWindowUpdateLayerTree + 67
23 AppKit 0x7ff80550c889 -[NSWindow displayIfNeeded] + 214
24 AppKit 0x7ff80550c720 __NSWindowGetDisplayCycleObserverForDisplay_block_invoke + 582
25 AppKit 0x7ff80550b4fd NSDisplayCycleObserverInvoke + 140
26 AppKit 0x7ff80550b12f NSDisplayCycleFlush + 878
27 QuartzCore 0x7ff80a2c4411 CA::Transaction::run_commit_handlers(CATransactionPhase) + 95
28 QuartzCore 0x7ff80a2c2ec1 CA::Transaction::commit() + 377
29 AppKit 0x7ff8055a8c6d __62+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayLink]_block_invoke + 285
30 AppKit 0x7ff806076339 ___NSRunLoopObserverCreateWithHandler_block_invoke + 41
31 CoreFoundation 0x7ff801e46836 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
32 CoreFoundation 0x7ff801e4675a __CFRunLoopDoObservers + 493
33 CoreFoundation 0x7ff801e45cdc __CFRunLoopRun + 850
34 CoreFoundation 0x7ff801e45372 CFRunLoopRunSpecific + 557
35 HIToolbox 0x7ff80c6b19d9 RunCurrentEventLoopInMode + 292
36 HIToolbox 0x7ff80c6b17e6 ReceiveNextEventCommon + 665
37 HIToolbox 0x7ff80c6b1531 _BlockUntilNextEventMatchingListInModeWithFilter + 66
38 AppKit 0x7ff80544d0c5 _DPSNextEvent + 880
39 AppKit 0x7ff805d3e150 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1304
40 AppKit 0x7ff80543e63a -[NSApplication run] + 603
41 AppKit 0x7ff805412670 NSApplicationMain + 816
42 dyld 0x7ff8019e33a6 start + 1942
Thread 1:: com.apple.NSEventThread
0 libsystem_kernel.dylib 0x7ff801d2ca2e mach_msg2_trap + 10
1 libsystem_kernel.dylib 0x7ff801d3ae4a mach_msg2_internal + 84
2 libsystem_kernel.dylib 0x7ff801d33b6e mach_msg_overwrite + 653
3 libsystem_kernel.dylib 0x7ff801d2cd1f mach_msg + 19
4 CoreFoundation 0x7ff801e47475 __CFRunLoopServiceMachPort + 143
5 CoreFoundation 0x7ff801e45ee5 __CFRunLoopRun + 1371
6 CoreFoundation 0x7ff801e45372 CFRunLoopRunSpecific + 557
7 AppKit 0x7ff8055aa3e0 _NSEventThread + 122
8 libsystem_pthread.dylib 0x7ff801d6c202 _pthread_start + 99
9 libsystem_pthread.dylib 0x7ff801d67bab thread_start + 15
Thread 2:
0 libsystem_pthread.dylib 0x7ff801d67b88 start_wqthread + 0
Thread 3:
0 libsystem_pthread.dylib 0x7ff801d67b88 start_wqthread + 0
Thread 4:
0 libsystem_pthread.dylib 0x7ff801d67b88 start_wqthread + 0
Thread 5:
0 libsystem_pthread.dylib 0x7ff801d67b88 start_wqthread + 0
Thread 6:
0 libsystem_pthread.dylib 0x7ff801d67b88 start_wqthread + 0
Thread 7:
0 libsystem_pthread.dylib 0x7ff801d67b88 start_wqthread + 0
Thread 8:
0 libsystem_pthread.dylib 0x7ff801d67b88 start_wqthread + 0
Thread 9:
0 libsystem_pthread.dylib 0x7ff801d67b88 start_wqthread + 0
Thread 10:
0 libsystem_pthread.dylib 0x7ff801d67b88 start_wqthread + 0
Thread 11:
0 libsystem_pthread.dylib 0x7ff801d67b88 start_wqthread + 0
Thread 12:
0 libsystem_pthread.dylib 0x7ff801d67b88 start_wqthread + 0
Thread 13:
0 libsystem_pthread.dylib 0x7ff801d67b88 start_wqthread + 0
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x00007ff8019a1900 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x0000600003a13b20 rsi: 0x00007ff821c2b5ac rbp: 0x00007ff7b37f88f0 rsp: 0x00007ff7b37f86f8
r8: 0x0000000000000000 r9: 0x00000000000000d0 r10: 0x000065b97f413b20 r11: 0x00007ff821c2b5ac
r12: 0x00007ff7b37f8900 r13: 0x0000600003a13b20 r14: 0x00007fe3a4ac7540 r15: 0x0000000000000001
rip: 0x00007ff8019a191d rfl: 0x0000000000010202 cr2: 0x000065b97f413b38
Logical CPU: 8
Error Code: 0x00000004 (no mapping for user data read)
Trap Number: 14
Thread 0 instruction stream:
01 76 17 49 83 c3 10 49-3b 33 75 f1 49 8b 43 08 .v.I...I;3u.I.C.
48 83 f8 00 74 03 4c 31-d0 c3 eb 00 31 c0 c3 66 H...t.L1....1..f
66 66 66 66 66 2e 0f 1f-84 00 00 00 00 00 66 66 fffff.........ff
66 66 66 66 2e 0f 1f 84-00 00 00 00 00 66 0f 1f ffff.........f..
44 00 00 48 85 ff 2e 74-72 40 f6 c7 01 2e 75 76 D..H...tr@....uv
49 ba f8 ff ff ff ff 7f-00 00 4c 23 17 49 89 f3 I.........L#.I..
[45]23 5a 18 49 c1 e3 04-4d 03 5a 10 49 3b 33 75 E#Z.I...M.Z.I;3u <==
0a 4d 8b 5b 08 4d 31 d3-41 ff e3 49 83 3b 01 76 .M.[.M1.A..I.;.v
13 49 83 c3 10 49 3b 33-75 f1 4d 8b 5b 08 4d 31 .I...I;3u.M.[.M1
d3 41 ff e3 72 70 4d 8b-5b 08 eb 0a 49 83 3b 01 .A..rpM.[...I.;.
76 13 49 83 c3 10 49 3b-33 75 f1 4d 8b 5b 08 4d v.I...I;3u.M.[.M
31 d3 41 ff e3 eb 4f 0f-1f 40 00 31 c0 31 d2 0f 1.A...O..@.1.1..
Binary Images:
0x1530a9000 - 0x1530acfff com.apple.icloud.drive.fileprovider.override (1.0) <9ed5a6be-94ce-3522-bf98-52d2b97d8642> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/iCloudDriveFileProviderOverride.bundle/Contents/MacOS/iCloudDriveFileProviderOverride
0x15318b000 - 0x1531a6fff com.apple.findersync.fileprovideroverride.FinderSyncCollaborationFileProviderOverride (14.0) <2ec27c6e-4874-39e5-bf40-b9d12d9bfbc6> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride
0x153091000 - 0x153098fff com.apple.FileProviderOverride (1681.1.8) <583d91ec-36da-3394-8233-6fc5736eb542> /System/Library/Frameworks/FileProvider.framework/OverrideBundles/FileProviderOverride.bundle/Contents/MacOS/FileProviderOverride
0x1530cf000 - 0x1530e6fff com.apple.security.csparser (3.0) <ae6cfd3f-05af-39ec-8a56-bee9abacb0f5> /System/Library/Frameworks/Security.framework/Versions/A/PlugIns/csparser.bundle/Contents/MacOS/csparser
0x10d1e1000 - 0x10d1f0fff libobjc-trampolines.dylib (*) <c43ce21c-a026-37b5-95ee-ef39fd2196de> /usr/lib/libobjc-trampolines.dylib
0x10cf8e000 - 0x10cfd1fff org.sparkle-project.Sparkle (2.4.0) <03e16ab6-5d78-35c3-8ef2-7e9505e51cf3> /Applications/Scrivener 3.app/Contents/Frameworks/Sparkle.framework/Versions/B/Sparkle
0x10d401000 - 0x10d450fff com.paddle.Paddle (4.4.0) <a4540115-7383-362d-930d-34bc962daa52> /Applications/Scrivener 3.app/Contents/Frameworks/Paddle.framework/Versions/A/Paddle
0x10d5e4000 - 0x10d60bfff com.literatureandlatte.AppReg (1.0) <c54784da-6840-3118-a386-6820a28295e7> /Applications/Scrivener 3.app/Contents/Frameworks/AppReg.framework/Versions/A/AppReg
0x10ddd0000 - 0x10e043fff com.literatureandlatte.ScrAppKit (*) <bf913e2b-747b-312c-a664-df0531e96f00> /Applications/Scrivener 3.app/Contents/Frameworks/ScrAppKit.framework/Versions/A/ScrAppKit
0x10c701000 - 0x10cdf4fff com.literatureandlatte.scrivener3 (3.3.3) <c56e04f1-f059-3d42-9f92-ecf7507d85a7> /Applications/Scrivener 3.app/Contents/MacOS/Scrivener
0x7ff80199b000 - 0x7ff8019dcfc0 libobjc.A.dylib (*) <cb7ac98c-b998-3a03-a07d-6125de3391d1> /usr/lib/libobjc.A.dylib
0x7ff806810000 - 0x7ff8069ebff2 com.apple.UIFoundation (1.0) <e2f0b346-c2aa-3c89-9b74-024e5231fb10> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation
0x7ff80540e000 - 0x7ff80680ffff com.apple.AppKit (6.9) <70a55260-7bb1-3c07-aac3-402d42fa9913> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x7ff80a2c1000 - 0x7ff80a664ff3 com.apple.QuartzCore (1.11) <b67c66ab-c1f1-3094-b36f-a64a99b0d585> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x7ff801dcb000 - 0x7ff802264ffc com.apple.CoreFoundation (6.9) <9daa29f3-fe48-39a9-a70d-1e0fd4750372> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7ff80c681000 - 0x7ff80c91cff4 com.apple.HIToolbox (2.1.1) <ad043d3b-2199-381b-96f2-2d827bae0c57> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
0x7ff8019dd000 - 0x7ff801a792ff dyld (*) <1289b60a-4980-342d-b1a4-250bbee392f1> /usr/lib/dyld
0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ???
0x7ff801d2b000 - 0x7ff801d65ff7 libsystem_kernel.dylib (*) <3690c1fc-599f-39ff-bbdb-85422e9a996c> /usr/lib/system/libsystem_kernel.dylib
0x7ff801d66000 - 0x7ff801d71fff libsystem_pthread.dylib (*) <33c43114-85f0-3f32-86d7-8e6a2403d38c> /usr/lib/system/libsystem_pthread.dylib
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=964.5M resident=0K(0%) swapped_out_or_unallocated=964.5M(100%)
Writable regions: Total=6.6G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=6.6G(100%)
VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Accelerate framework 128K 1
Activity Tracing 256K 1
CG image 7212K 57
CG raster data 64K 7
ColorSync 260K 35
CoreAnimation 10.8M 255
CoreGraphics 20K 3
CoreUI image data 5644K 44
Foundation 36K 2
Image IO 64K 1
Kernel Alloc Once 8K 1
MALLOC 2.4G 110
MALLOC guard page 120K 30
SQLite page cache 256K 2
STACK GUARD 56.1M 14
Stack 14.6M 14
VM_ALLOCATE 128.1M 14
VM_ALLOCATE (reserved) 3.9G 1 reserved VM address space (unallocated)
WebKit Malloc 192.0M 6
__CTF 824 1
__DATA 42.1M 667
__DATA_CONST 46.8M 450
__DATA_DIRTY 1767K 238
__FONT_DATA 2352 1
__LINKEDIT 181.8M 12
__OBJC_RO 70.6M 1
__OBJC_RW 2154K 2
__TEXT 782.7M 684
dyld private memory 260K 2
libnetwork 128K 8
mapped file 1.2G 374
shared memory 824K 29
=========== ======= =======
TOTAL 8.9G 3067
TOTAL, minus reserved VM space 5.1G 3067
Hope you had a good āpartialā weekend
Build 16204 remains stable and fast. Iāll provide any additional updates today as they occur.
When you release 3.3.4, will it be this build?
If not and youād like me to try the 3.3.4 release candidate build, just let me know.
You might try the 16204 build that @KB sent me a couple days ago. You will find it several posts up with the file name: Scriv_071023.zip
Iāll try and copy the link below, but not sure if it will work:
Huzzah! Thanks for keeping me up to date - Iām glad itās still working.
The release build wonāt change anything in regard to this particular fix (as long as it remains stable), but it will contain a couple of other fixes related to other areas of the software. For instance, Iāve made a change since 16204 related to the synopsis area, which was triggering a crash on entering composition mode for a small handful of users. The latest build (containing that fix) can be found here:
Please try the build linked above.
Sounds goodā¦Iāll go ahead and install this build and any subsequent ones you post prior to 3.3.4 and let you know if anything breaks.
Hi there.
Iām having a related issue, although Scrivener doesnāt actually crash for me. Iām working in Sonoma, with Scrivener version 3.3.3. When I write in either Page View or Composition mode (which I rely on to keep track of my progress), the text sometimes gets all mashed up, with several layers of text appearing over each other, making it completely illegible. This keeps happening until I exit out of Page View or Composition mode, which is a real hassle.
Will the new build that you linked to resolve this issue? Iām somewhat of a technical dummy, so can you briefly explain how to use the ābuildā? Is it as simple as downloading the file and opening it?
Thanks,
Patrick
Great, thanks.
Yes, it should do, as the mashed up text is part of the same bug. And yes - the zip file just contains Scrivener, so you can download it, drag the new copy of Scrivener to your Applications folder and use that.
Iāll be putting out an official update with this fix later today or tomorrow though.
All the best,
Keith
2 Likes