Jump to content
  • 0

Evernote crashes on new window, if PDF note open


grobstein

Idea

I have had this issue for months, and across several versions of the software -- all 6.x versions, plus a 5.x build that I installed in desperation. I've only just figured out exactly how to reproduce it; it now happens without fail every time I try to create a new window while a PDF note is open, and sometimes when I try to create a new window if a PDF note has only recently been open. 

 

Right now I am on:

Evernote 6.0.5 (451190 Direct)

OS X 10.10.1

2012 Macbook Air, 8GB RAM, 2GHz i7

 

Any command that would create a new window crashes Evernote, if a note containing a PDF attachment is open in the edit pane. (The crash also seems to occur if a PDF note had focus immediately before I attempt to open a different note in new window, even though the PDF note is not open.) The window fails to open, and then in 1-2 seconds the app fails silently. This happens literally every time

 

Commands affected: 

New Evernote window

Open note in new window

 

 

 

OS X produces a traceback like this: 

 

 

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

0   libsystem_kernel.dylib         0x00007fff8fe0b282 __pthread_kill + 10
1   libsystem_c.dylib             0x00007fff95586b73 abort + 129
2   net.hockeyapp.sdk.mac         0x000000010b43d762 uncaught_exception_handler + 27
3   com.apple.HIToolbox           0x00007fff879d4664 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2084
4   com.apple.HIToolbox           0x00007fff879d376e SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 386
5   com.apple.HIToolbox           0x00007fff879e8286 SendEventToEventTarget + 40
6   com.apple.HIToolbox           0x00007fff87a1d795 SendHICommandEvent(unsigned int, HICommand const*, unsigned int, unsigned int, unsigned char, void const*, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef**) + 428
7   com.apple.HIToolbox           0x00007fff87a50e8d SendMenuCommandWithContextAndModifiers + 59
8   com.apple.HIToolbox           0x00007fff87a50e34 SendMenuItemSelectedEvent + 188
9   com.apple.HIToolbox           0x00007fff87a50d06 FinishMenuSelection(SelectionData*, MenuResult*, MenuResult*) + 96
10  com.apple.HIToolbox           0x00007fff87a588b1 MenuSelectCore(MenuData*, Point, double, unsigned int, OpaqueMenuRef**, unsigned short*) + 702
11  com.apple.HIToolbox           0x00007fff87a5849e _HandleMenuSelection2 + 446
12  com.apple.AppKit               0x00007fff8b3d6d1e _NSHandleCarbonMenuEvent + 277
13  com.apple.AppKit               0x00007fff8b272a40 _DPSNextEvent + 1843
14  com.apple.AppKit               0x00007fff8b271e80 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 194
15  com.apple.AppKit               0x00007fff8b265e23 -[NSApplication run] + 594
16  com.apple.AppKit               0x00007fff8b2512d4 NSApplicationMain + 1832
17  com.evernote.Evernote         0x000000010aabc784 0x10aaba000 + 10116

 

I've also sent probably dozens of crash reports about this. 

 

I am a 5-year Evernote user and a Premium member, but the past few months have been so frustrating that I am just about ready to roll my own with Dropbox. Help me out here. 

Link to comment

4 replies to this idea

Recommended Posts

  • Level 5*

Hi.  Usual basic suggestion is to uninstall and reinstall the software - clearly this shouldn't be happening,  and AFAIK hasn't been reported as a problem by anyone else.

 

The Crash reports are just reports to Evernote - no-one will come back to you unless they need some more information.  As a premium user you can raise a support request and maybe get some one on one help via the chat feature (weekdays, PST).  See here for details > https://evernote.com/contact/support/

 

Evernote has some general information about crashes here https://evernote.com/contact/support/kb/#!/article/28942676

Link to comment

Thanks -- I have filed a support ticket as well. I have been through several uninstall / reinstall / upgrade / downgrade cycles over the past few months, with the issue apparently persisting, but I haven't done it recently so maybe I will try now. 

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...