Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Delicious Library 3.8.5 Crashes

Since buying the new Retina iMac I've had trouble running the latest version of Delicious Library 2.

Simply it crashes on opening.

Was hoping someone might be able to help out.


Someone has told me it might be pixel buffer allocation - what ever that means.

Have tried to attach a copy of the crash report but no luck.

Intel iMac-OTHER, OS X Yosemite (10.10.5), iMac Retina Display

Posted on Aug 28, 2015 8:13 PM

Reply
7 replies

Aug 29, 2015 7:14 AM in response to David Delaney

Launch the Console application in any of the following ways:

☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

Step 1

For this step, the title of the Console window should be All Messages. If it isn't, select

SYSTEM LOG QUERIES All Messages

from the log list on the left. If you don't see that list, select

View Show Log List

from the menu bar at the top of the screen.

In the top right corner of the Console window, there's a search box labeled Filter. Enter the name of the crashed application or process. For example, if Safari crashed, you would enter "Safari" (without the quotes.)

Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.

The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.

Please don't indiscriminately dump thousands of lines from the log into this discussion.

Please don't post screenshots of log messages—post the text.

Some private information, such as your name, may appear in the log. Anonymize before posting.

Step 2

In the Console window, select

DIAGNOSTIC AND USAGE INFORMATION User Diagnostic Reports

(not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.

I know the report is long, maybe several hundred lines. Please post all of it anyway.

If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.

In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

When you post the log extract or the crash report, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the forum software. Please post the text on Pastebin, then post a link here to the page you created.

Aug 29, 2015 11:31 PM in response to Linc Davis

Hi Linc,


Thanks for the reply. To be honest I wouldn't know what to copy over that'd be useful.

The developer has however come back and said they've picked up the following from the crash report I submitted to them.


"Insufficient memory to allocate pixel data buffer of 260096 bytes.'"

Don't know if that's any help.

Strange thing is the application works fine on Yosemite on an old iMac, but not on the Retina.

I suspect it's got something to do with the size of some scans that are in the application. Might be too big for it to open. But still seems strange it works on an old machine.

Aug 30, 2015 2:05 PM in response to Linc Davis

Thanks Linc,

I appreciate the help. Not a matter of not wanting to post the info, am just not sure what's useful.

In step 1 there's 4 items which in themselves are about 4 or 5 lines each, but when I expand them they're very long and make no sense to me - obviously.

In Step 2 I can't choose DIAGNOSTIC AND USAGE INFORMATION It's a header with the Diagnostic and Usage Messages under it.

Delicious Library 3.8.5 Crashes

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.