MacDownApp/macdown

Uncaught error when opening multiple documents in MacDown on Mac OS X 10.11 beta

Open

#409 opened on Jul 13, 2015

View on GitHub
 (7 comments) (0 reactions) (0 assignees)Objective-C (7,686 stars) (930 forks)batch import
bughelp wanted

Description

  1. Run MacDown: the default blank document opens.
  2. Choose File > Open to open another document.

EXPECTED: The new document opens, and the default blank document is still there. (Incidentally I think it would be a good enhancement to close the default blank document when opening another document, if the default blank document has no unsaved changes.)

ACTUAL: The opened document window appears, but a message box appears reporting a caught exception, and saying that you can click Continue to run in an inconsistent state, but woe betide you.

  1. Click Continue.

EXPECTED: Not sure. Hopefully I can keep working! ACTUAL: MacDown crashes out.

WORKAROUND: Close the default document before opening the document you want to edit, and only have one document window open at once.

Contributor guide

Tech stack
objective c
Domain
desktop
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Objective CmacOS developmentdebugging
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Focus on the document opening workflow in MacDown, likely using NSDocument. Investigate the exception when opening a second document while the default blank document is open. Check for any existing fixes or discussions in the issue comments (7 comments). Look at the repository's commit history for similar fixes. The crash may be due to improper handling of multiple windows or document state.