Jump to content

Search the Community

Showing results for tags '32-bit'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General Discussion
    • Community Announcements
    • Evernote General Discussions
    • Evernote Integrations
    • Evernote Betas
    • Evernote API Discussion
  • FAQ's: Best Answers
    • FAQ's: Best Answers
  • Possible Bugs/Technical Issues
    • General Technical Issues
    • Evernote Business
    • Evernote for Android
    • Evernote for iOS
    • Evernote for Mac
    • Evernote for Windows
    • Web Client
    • Evernote Product Suite
  • Product Feedback/Feature Requests
    • General Feature Requests
    • Evernote Business
    • Evernote for Android
    • Evernote for iOS
    • Evernote for Mac
    • Evernote for Windows
    • Evernote Web Client
    • Evernote Product Suite
  • Evernote Forum Archives
    • Using Evernote
    • General Discussion Archive
    • Product Archives
  • Web Clipper***
  • International Forums
    • Japanese Discussions
    • Brazilian Portuguese Discussions
    • Discussions in Spanish
    • Korean Discussions
    • Traditional Chinese Discussions

Blogs

There are no results to display.

There are no results to display.

Categories

There are no results to display.

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Subscription

Found 1 result

  1. I've been trying to keep my Evernote backed up, and attempting to do so in multiple formats to ensure that I have something that can be parsed/imported later. With 4000 notes, including a large number of scanned images and PDFs, the current 32-bit Evernote application crashes when exporting all notes in "Single-page html" or web-archive/mht. It took me a little while to track down what was happening, but essentially Evernote is consuming a large amount of RAM during exporting those formats. The used memory increases until it gets to about 3.5GB and then crashes. The error messages in the activity log file look like this "date/time [pid] CBuffer: Failed to allocate xxxx bytes of memory." There should be a few of them before the app crashes. The computer has 32GB of ram, and could certainly support a temporary increased usage to facilitate the export. A 64-bit version would be nice to avoid these types of limitations. Thanks Keith
×
×
  • Create New...