Repeated crashing in MacOS Sierra

Open

#659 opened on Sep 22, 2016 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug help wanted

Dominant language: Rich Text Format
Stars: 9.8k
Forks: 1.2k
PR merge metrics: No merged PRs in 30d

Description

MacDown is crashing frequently on a MacBookPro Retina under MacOS Sierra. It seems to be graphics related...

```
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000028
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]

VM Regions Near 0x28:
-->
__TEXT 000000010f6a4000-000000010f73f000 [ 620K] r-x/rwx SM=COW /Applications/MacDown.app/Contents/MacOS/MacDown

Thread 0 Crashed:: Dispatch
0 com.apple.CoreGraphics
1 com.apple.QuartzCore
2 com.apple.QuartzCore
3 com.apple.QuartzCore
4 com.apple.AppKit
5 com.apple.AppKit
6 com.apple.AppKit
7 com.apple.QuartzCore
8 com.apple.QuartzCore
9 com.apple.QuartzCore
10 com.apple.QuartzCore
11 com.apple.QuartzCore
12 com.apple.CoreFoundation
13 com.apple.CoreFoundation
14 com.apple.CoreFoundation
15 com.apple.HIToolbox
16 com.apple.HIToolbox
17 com.apple.HIToolbox
18 com.apple.AppKit
19 com.apple.AppKit
20 com.apple.AppKit
21 com.apple.AppKit
22 libdyld.dylib queue: com.apple.main-thread 0x00007fff8bcc461c CGColorSpaceGetNumberOfComponents + 15 0x00007fff90f6d639 CABackingStoreUpdate_ + 525 0x00007fff9108abcc ___ZN2CA5Layer8display_Ev_block_invoke + 75 0x00007fff9108a846 CA::Layer::display_() + 1748 0x00007fff8937bc2c -[NSTileLayer display] + 119 0x00007fff89b46a7b -[_NSTiledLayerContents update:shouldCallPrepareContent:] + 5174 0x00007fff892fe5de -[_NSTiledLayer display] + 389 0x00007fff9107e9a6 CA::Layer::display_if_needed(CA::Transaction*) + 572 0x00007fff9107ead1 CA::Layer::layout_and_display_if_needed(CA::Transaction*) + 35 0x00007fff910742e8 CA::Context::commit_transaction(CA::Transaction*) + 280 0x00007fff90f6b5e5 CA::Transaction::commit() + 475 0x00007fff90f6bf46 CA::Transaction::observer_callback(__CFRunLoopObserver*, unsigned long, void*) + 108 0x00007fff8b470f67 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 0x00007fff8b470ed7 __CFRunLoopDoObservers + 391 0x00007fff8b4515d6 CFRunLoopRunSpecific + 454 0x00007fff8a9f2f6c RunCurrentEventLoopInMode + 240 0x00007fff8a9f2ca9 ReceiveNextEventCommon + 184 0x00007fff8a9f2bd6 _BlockUntilNextEventMatchingListInModeWithFilter + 71 0x00007fff890e95f5 _DPSNextEvent + 1093 0x00007fff897f98eb -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1637 0x00007fff890ddfbd -[NSApplication run] + 926 0x00007fff890a8a8a NSApplicationMain + 1237 0x00007fffa0491255 start + 1

```

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Research direction

Start by reproducing the crash on a MacBook Pro Retina running macOS Sierra and compare the report's main-thread stack through CoreGraphics, QuartzCore, and AppKit. No project file or test is named; done would mean identifying the graphics-related cause and verifying that the repeated crash no longer occurs.

Written by the indexing model from the issue text.

Assessment

Tech stack: macos, objective-c
Domain: desktop
Issue type: Bug
Difficulty: 4/5
Estimated time: 3-5 days
Activity status: Stale
Clarity: Needs clarification
Newbie friendliness: 30/100