You can tell the version of OSX you’re running on your Mac by going to the black Apple on the top left corner then “About this Mac”. Reply to this email directly, view it on GitHub, or mute the thread.Ensure you’re running the latest operating system (OS) You are receiving this because you were mentioned. It's probably not related, but which version of macOS are you using? When you were editing this file, how often does this (high memory consumption) happen? Always?ģ. Is there anything you were doing when MacDown eats your memory?Ģ. I have opened the Markdown files (both from and and kept it in background for an hour. On Jun 21, 2017, at 11:45 PM, Franklin Yu > wrote: I’ve come back because of the suggestion of removing auto-render. If the developers were not using it, I’ll bet that something broke in the update.Īs for when this happens? Every time I tried, so I moved to Atom to work. I don’t think that’s the problem as I’m pretty sure that I found the bad behavior before the MathJax hosting change. Reading ahead, to Tzu-ping’s concern about MathJax. I’ve actually upgraded two of them yesterday. I’m running 10.12.3 on 3 computers, all of which exhibit the issue. I don’t remember who it was that suggested this, but I too believe that it’s a lot more stable when I turn off the automatic rendering and just do command-R when I want it to. If I wait for a long time, the spinning beachball would eventually stop and I could continue. I kept thinking that there was some buffering that would saturate. I had to be typing fast, deleting text, or something that was high rate at the keyboard. And it never happened when nothing was going on. The issue that I found was not related to memory consumption…I don’t think. Path: /Applications/MacDown.app/Contents/MacOS/MacDownĢ260 Thread_3880202 DispatchQueue_1: -thread (serial) Sampling completed, processing symbols.Īnalysis of sampling MacDown (pid 23354) every 1 millisecond

Sampling process 23354 for 3 seconds with 1 millisecond of run time between samples

Macdown choppy typing