Jump to content

Brent Townshend

Level 2
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Brent Townshend

  1. If formatted text is pasted into a code block, then leading spaces are sometimes deleted, leading to offsetting of lines of fixed format material. It seems that if there is exactly one leading space, it is removed, but multiple leading spaces are left intact.
  2. Still crashing for me immediately on startup with an assertion failure. Brent
  3. Well, version 5.6.1beta 3 and 5.6.1 exhibit the same behavior -- crashing on startup. And I still haven't got any response from my (Premium) support ticket. Brent
  4. Brent, sorry to hear about your troubles. In recent months a number of long-time users with large accounts have reported many problems with Evernote. Like you, I was hoping the clean rewrite of Ver 5.6 would fix the scalability and sync issues. I can say that I'm still running Ver 5.5.2 with 11K+ notes, and it seems much more stable than the reports I have seen for Ver 5.6+. If you want to revert to Ver 5.5.2, Here is the direct download version of EN Mac 5.5.2: http://goo.gl/O0fRde Of course, make sure you do a full backup of your current Evernote folder, and export any Local NBs you may have before reverting. I would imagine that you will need to completely remove the current EN 5.6.x app and data before installing EN 5.5.2. Maybe someone from Evernote can comment on the best procedure to revert to Ver 5.5.2 from Ver 5.6.x Thanks, but I was also having crashing issues with 5.5.2 -- not sure I want to switch one set of crashes for another, especially since there (might) be a better chance of getting support/fixes within 5.6. FYI, the crashes I'm seeing are due to an internal assertion failure within evernote's code -- something that SHOULD be easy to diagnose, but ... And I have also filed a support ticket. Brent ---- excerpt from log --- 2014/10/09 10:05:25:467 I|* -[ENCacheManager initWithAccountContext:listenForStartNotifications:] | <ENMacAccountContext: 0x7fc8a952d030> YES self=0x600000545330 2014/10/09 10:05:25:467 I|* -[ENCacheManager startWithBackground:] | self=<ENCacheManager: 0x600000545330>2014/10/09 10:05:25:467 I|* -[ENSyncEngine _syncStoppedWithErrors:] | Sync complete. No errors.2014/10/09 10:05:25:476 I|* -[ENCacheManager checkFileSystemIntegrity] | File system appears to be in good shape. expected=1902, actual=19022014/10/09 10:05:25:509 I|* __39-[ENCacheManager recalculateStatistics]_block_invoke | totalSize=1363105286, cachedSize=1363105286, uncachedSize=02014/10/09 10:05:25:540 I|* __77-[ENCacheManager fetchNextBatchOfDownloadOperationsUsingBackgroundTransfers:]_block_invoke | Processing 0 notes2014/10/09 10:05:26:085 I|* -[ENCacheManager stop] | self=<ENCacheManager: 0x600000545330>2014/10/09 10:05:30:963 E|*** -[ENMacNoteMO setDirty:] | Assertion <ENMacNoteMO.m:199> -[ENMacNoteMO setDirty:] (self.notebook.canUpdateNotes) failed assertion (0 Evernote 0x0000000102ffbe88 Evernote + 20394321 CoreNote 0x0000000103dd8498 -[_ENNoteMO setDirtyValue:] + 642 CoreNote 0x0000000103e3861f -[ENCoreDataLocalStore findOrCreateResourceInNote:withData:mimeType:] + 3923 Evernote 0x0000000102ef6f2e Evernote + 9705424 CoreNote 0x0000000103e5c209 __100-[ENAccountContext
  5. I'm getting very frustrated with repeated crashing of Evernote. 5.6.1b2 is no better. It is currently in a state where it crashes within seconds after opening without doing anything, presumably as soon as it starts to sync. In the last few months, I've been constantly trying to deal with crashing issues, having deleted everything on my computer, reinstalling, etc, but the crashing behavior keeps coming back. Perhaps my experience is unique in that I'm using it for lab notebooks and have a large footprint of notes (~1.7 Gbygtes), many with multiple attachments, but if the service can't scale to that, it's got problems. I had hoped that the 5.6 rewrite was going to improve stability of Evernote, but it seems that was only a dream. Brent
  6. In fact, I did exactly that, including going through Application Defaults and making sure nothing was left before downgrading. It seems that the problem is not on the local machine, but rather 5.6 did something to the server database that is causing 5.5.2 to no longer be able to sync. It is is hitting exceptions related to missing resource data: 374442e-4773-46b1-8969-1dd803f6f328 / application/x-iwork-numbers-sffnumbers2014-07-08 16:29:34 sync [ENSyncEngine] INFO: starting downloads...2014-07-08 16:29:41 [ENSyncBatchDownloadOperation] ERROR: Exception fetching resource data: EDAMSystemException(errorCode:4,message:"ObjectNotFoundException",rateLimitDuration:0)2014-07-08 16:29:41 [ENSyncBatchDownloadOperation] ERROR: resource: [b08d193d-2589-4046-83fe-1d50a6cf8702]2014-07-08 16:29:41 [ENSyncBatchDownloadOperation] ERROR: note: [95c5ab3b-e29b-4142-8ab5-6571eb5fd462] 'Spectral Filtering'2014-07-08 16:29:41 [ENSyncBatchDownloadOperation] ERROR: Exception during batch download: EDAMSystemException(errorCode:4,message:"ObjectNotFoundException",rateLimitDuration:0)2014-07-08 16:29:41 [ENSyncBatchDownloadOperation] ERROR: (0 CoreFoundation 0x00007fff8cff225c __exceptionPreprocess + 1721 libobjc.A.dylib 0x00007fff839e6e75 objc_exception_throw + 432 Evernote 0x0000000100324df6 -[EDAMNoteStoreClient getResourceData::] + 03 Evernote 0x0000000100130b93 -[ENSyncBatchDownloadOperation main] + 17024 Foundation 0x00007fff8cbac8a1 -[__NSOperationInternal _start:] + 6315 Foundation 0x00007fff8cbac54b __NSOQSchedule_f + 646 libdispatch.dylib 0x00007fff8ba2b28d _dispatch_client_callout + 87 libdispatch.dylib 0x00007fff8ba2f7e3 _dispatch_async_redirect_invoke + 1548 libdispatch.dylib 0x00007fff8ba2b28d _dispatch_client_callout + 89 libdispatch.dylib 0x00007fff8ba2d082 _dispatch_root_queue_drain + 32610 libdispatch.dylib 0x00007fff8ba2e177 _dispatch_worker_thread2 + 4011 libsystem_pthread.dylib 0x00007fff83402ef8 _pthread_wqthread + 31412 libsystem_pthread.dylib 0x00007fff83405fb9 start_wqthread + 13) Even after I delete the "bad" note through the web app, the next sync hits the same error for a different note, ad inifinitum (or at least as far as I've tested).
  7. Since upgrading to the 5.6 beta 1, I'm having no end of problems. At this point, Evernote crashes as soon as I try to view any of the notes I created with 5.6. In addition, the notes themselves seem to be growing with inserted blank lines -- thousand's of them. The crash looks like below. Even worse, when I try to downgrade to 5.5, I'm getting repeated sync errors and unable to complete a sync. I've opened a trouble ticket on this, but very worrisome that this kind of instability is present. Brent Process: Evernote [2436] Path: /Applications/Evernote-2.app/Contents/MacOS/Evernote Identifier: com.evernote.Evernote Version: 5.6.0 Public Beta 1 (450470) Code Type: X86-64 (Native) Parent Process: launchd [238] Responsible: Evernote [2436] User ID: 501 Date/Time: 2014-07-08 17:35:23.228 -0700 OS Version: Mac OS X 10.9.3 (13D65) Report Version: 11 Anonymous UUID: 58B01D61-66D7-E0D7-245C-E8DD304817FA Sleep/Wake UUID: AB7195FC-3B5A-469D-9884-E5D3FB81DB64 Crashed Thread: 20 Dispatch queue: NSManagedObjectContext Queue Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Application Specific Information: abort() called Thread 0:: main Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x00007fff835a6a1a mach_msg_trap + 10 1 libsystem_kernel.dylib 0x00007fff835a5d18 mach_msg + 64 2 com.apple.CoreGraphics 0x00007fff88351c9b _CGSSynchronizeWindowBackingStore + 97 3 com.apple.CoreGraphics 0x00007fff882d3480 _CGSLockWindow + 3765 4 com.apple.CoreGraphics 0x00007fff882d2393 CGSDeviceLock + 240 5 libRIP.A.dylib 0x00007fff8bc3a487 ripd_Lock + 43 6 libRIP.A.dylib 0x00007fff8bc3a027 RIPLayerBltShape + 463 7 libRIP.A.dylib 0x00007fff8bc38468 ripc_Render + 304 8 libRIP.A.dylib 0x00007fff8bc342e1 ripc_DrawRects + 399 9 com.apple.CoreGraphics 0x00007fff882ced2a CGContextFillRects + 96 10 com.apple.AppKit 0x00007fff854ffc7f NSRectFill + 271 11 com.evernote.Evernote 0x00000001051179d8 0x104f8f000 + 1608152 12 com.apple.AppKit 0x00007fff854d10b1 -[NSView _drawRect:clip:] + 3846 13 com.apple.AppKit 0x00007fff854ce03c -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 3199 14 com.apple.AppKit 0x00007fff854cebc4 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 6151 15 com.apple.AppKit 0x00007fff854cebc4 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 6151 16 com.apple.AppKit 0x00007fff854cebc4 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 6151 17 com.apple.AppKit 0x00007fff854cceb1 -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 314 18 com.apple.AppKit 0x00007fff854c9e9f -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 2828 19 com.apple.AppKit 0x00007fff854a92fa -[NSView displayIfNeeded] + 1680 20 com.apple.Foundation 0x00007fff8cc1eafa __NSFirePerformWithOrder + 332 21 com.apple.CoreFoundation 0x00007fff8cf22e17 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 22 com.apple.CoreFoundation 0x00007fff8cf22d87 __CFRunLoopDoObservers + 391 23 com.apple.CoreFoundation 0x00007fff8cf14468 __CFRunLoopRun + 776 24 com.apple.CoreFoundation 0x00007fff8cf13f25 CFRunLoopRunSpecific + 309 25 com.apple.HIToolbox 0x00007fff845dea0d RunCurrentEventLoopInMode + 226 26 com.apple.HIToolbox 0x00007fff845de685 ReceiveNextEventCommon + 173 27 com.apple.HIToolbox 0x00007fff845de5bc _BlockUntilNextEventMatchingListInModeWithFilter + 65 28 com.apple.AppKit 0x00007fff8537226e _DPSNextEvent + 1434 29 com.apple.AppKit 0x00007fff853718bb -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122 30 com.apple.AppKit 0x00007fff853659bc -[NSApplication run] + 553 31 com.apple.AppKit 0x00007fff853507a3 NSApplicationMain + 940 32 com.evernote.Evernote 0x0000000104f91474 0x104f8f000 + 9332 etc...
  8. Just found and installed 5.0.5 -- that fixes the problem.
  9. Where is Beta 5.0.5? From within evernote, with beta updates checked, it is still showing 5.0.4 as the latest version.
  10. I'm seeing an issue with 5.0.4 on MacOS 10.8.2 -- the client is spinning downloading continually. The activity monitor just shows "Downloading metadata...". Tried quitting and restarting, but same symptoms. Anyone else see this? Brent
  11. I'm seeing the same issue. In addition, I noticed that changing an attached spreadsheet and not making any other changes does not result in a new version being uploaded to the server. I'm running 5.0.4 premium, from direct download. Brent
×
×
  • Create New...