These are the known bugs in Scrivener as of beta 5. Needless to say, if you can help me track down any of these bugs, I would be very grateful. In each case, the bug is rare - that is to say, either it has been reported to me but I cannot reproduce it at all, or I cannot reproduce it with the frequency required to find its cause.
Please do not worry about these bugs unless you encounter them. None have been reported to cause any data loss, and all of them have occurred to only one of many users. Remember that all software has bugs lurking - even some of the big name software can crash from time to time. I post this list here so that users can look out for these bugs and know to report them to me straight away should you encounter them.
Please note that crash logs are always helpful (and should always be sent to me at support@literatureatlatte.com if you encounter a crash) but they only tell me half of the story. They tell me where in the code the program crashed, but this isn’t always helpful on its own. I also need to know everything you did leading up to the crash, so please do try to provide this information.
Thanks!
The bugs:
Notes pane sometimes becomes too big
There is a bug whereby the notes text view in the inspector can become too big so that the top of it overlaps the meta-data panel above it. This happens either when inspector is resized or made visible, and it seems to have something to do with the main window being zoomed to fit the whole screen. This only happens very rarely - I have seen it on several occasions, but I cannot get it to happen when I try… (To make the bug go away, close and reopen the affected project.)
Rare bug in save code which can cause a crash
One user has reported a crash upon deleting a PDF file (that is, moving it to the trash in the binder by hitting “Delete” in the toolbar) after viewing it in a horizontal split with a clippings text file. The crash log begins thus:
[code]Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000020
Thread 0 Crashed:
0 libobjc.A.dylib 0x90a53380 objc_msgSend + 16
1 com.apple.Foundation 0x926879c4 -[NSKeyedArchiver _encodeArrayOfObjects:forKey:] + 347
2 com.apple.Foundation 0x9266129b -[NSDictionary encodeWithCoder:] + 517
3 com.apple.Foundation 0x92686ef4 _encodeObject + 1035
4 com.apple.Foundation 0x926a1c48 +[NSKeyedArchiver archiveRootObject:toFile:] + 177
5 …iteratureandlatte.scrivener 0x0000480c -[SCRMainDocument saveDocument:] + 510
6 com.apple.Foundation 0x9260b0c7 __NSFireDelayedPerform + 403
7 com.apple.CoreFoundation 0x90828bc9 CFRunLoopRunSpecific + 3341
8 com.apple.CoreFoundation 0x90827eb5 CFRunLoopRunInMode + 61
9 com.apple.HIToolbox 0x92dcdb90 RunCurrentEventLoopInMode + 285
10 com.apple.HIToolbox 0x92dcd297 ReceiveNextEventCommon + 385
11 com.apple.HIToolbox 0x92dcd0ee BlockUntilNextEventMatchingListInMode + 81
12 com.apple.AppKit 0x9324f465 _DPSNextEvent + 572
13 com.apple.AppKit 0x9324f056 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 137
14 com.apple.AppKit 0x93248ddb -[NSApplication run] + 512
15 com.apple.AppKit 0x9323cd2f NSApplicationMain + 573
16 …iteratureandlatte.scrivener 0x000020f2 _start + 228 (crt.c:272)
17 …iteratureandlatte.scrivener 0x0000200d start + 41[/code]
The crash log indicates that something dodgy has happened in the binder that has caused a crash when Scrivener tried to save the project to disk. I have not been able to reproduce this crash, and so far no other users have reported anything similar. This crash did not cause any loss of data, so it is fairly benign, but obviously I would like to reproduce it myself so that I can squash the bug.
Bug that can cause a crash when cancelling the Preferences panel
There seems to be a bug that can cause a crash in rare circumstances upon closing the Preferences panel. This was reported in this thread:
literatureandlatte.com/forum … .php?t=710
This crash has only been reported by one user, and I have so far been unable to reproduce this bug.
Bug that can cause a crash upon importing a MultiMarkdown file
One user has reported a bug that can cause a crash during a File > Import > MultiMarkdown File action. I have so far been unable to reproduce this bug. The crash log begins thus:
[code]Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000006
Thread 0 Crashed:
0 com.apple.CoreFoundation 0x907f1994 CFDictionaryCreate + 48
1 com.apple.Foundation 0x92948e20 -[NSPlaceholderDictionary initWithObjects:forKeys:count:] + 320
2 com.apple.Foundation 0x92948c98 +[NSDictionary dictionaryWithObjectsAndKeys:] + 480
3 …iteratureandlatte.scrivener 0x0007885c -[SCRMainDocument(ImportExport) importMultiMarkdownFile:intoParent:atIndex:] + 1716 (crt.c:355)
4 com.apple.AppKit 0x938d565c -[NSSavePanel(NSSavePanelRuntime) _didEndSheet:returnCode:contextInfo:] + 272
5 com.apple.AppKit 0x938a2424 -[NSSavePanel(NSSavePanelRuntime) ok:] + 288
6 com.apple.AppKit 0x93788c4c -[NSApplication sendAction:to:from:] + 108
7 com.apple.AppKit 0x93788b80 -[NSControl sendAction:to:] + 96
8 com.apple.AppKit 0x93788a60 -[NSCell _sendActionFrom:] + 156
9 com.apple.AppKit 0x937a2a88 -[NSCell trackMouse:inRect:ofView:untilMouseUp:] + 1020
10 com.apple.AppKit 0x937a2670 -[NSButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 564
11 com.apple.AppKit 0x937a2094 -[NSControl mouseDown:] + 536
12 com.apple.AppKit 0x93743890 -[NSWindow sendEvent:] + 4616
13 com.apple.AppKit 0x93b8bd78 -[NSSavePanel sendEvent:] + 400
14 com.apple.AppKit 0x936ec8d4 -[NSApplication sendEvent:] + 4172
15 …iteratureandlatte.scrivener 0x000169c4 -[SCRApplication sendEvent:] + 600 (crt.c:355)
16 com.apple.AppKit 0x936e3d10 -[NSApplication run] + 508
17 com.apple.AppKit 0x937d487c NSApplicationMain + 452
18 …iteratureandlatte.scrivener 0x00002c24 _start + 340 (crt.c:272)
19 …iteratureandlatte.scrivener 0x00002acc start + 60[/code]
Rare bug in full screen causing flashing text
One user has reported that if “Hide main window” in the Preferences isn’t checked, the text in full screen mode can flash (“strobe”) when typing. I have been unable to reproduce this at all. The user reports that checking “Hide main window” makes the problem go away.