"NSImageCell's object value must be an NSImage" exception

RESOLVED DUPLICATE of bug 350651

Status

Camino Graveyard
General
RESOLVED DUPLICATE of bug 350651
12 years ago
12 years ago

People

(Reporter: Simon Fraser, Unassigned)

Tracking

Trunk
PowerPC
Mac OS X

Details

(Reporter)

Description

12 years ago
Sometimes Camino dumps onto the console
"NSImageCell's object value must be an NSImage" (my guess is that we're calling setImage:nil at some point, possibly related to favicons.

This normally seems benign, except when it happens from within a timer callback:

2006-09-29 19:20:49.759 Camino[415] *** NSTimer discarding exception 'NSImageCell's object value must be an NSImage.' that raised during firing of timer with target 15b6a2c0 and selector 'searchTimer:'
Camino(415,0xa000cfc0) malloc: ***  Deallocation of a pointer not malloced: 0xbfffe810; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug
Camino(415,0xa000cfc0) malloc: ***  Deallocation of a pointer not malloced: 0xbfffe650; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug
Camino(415,0xa000cfc0) malloc: ***  Deallocation of a pointer not malloced: 0xbfffe490; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug

Comment 1

12 years ago
Erm...

Isn't this a dupe of bug 350651? I haven't seen this since the fix for bug 346111 was checked in.

Simon, what build of Camino did you notice this with?

cl

Comment 2

12 years ago
It's definitely a dupe; if you're still seeing this in recent builds, we should reopen bug 350651

*** This bug has been marked as a duplicate of 350651 ***
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → DUPLICATE
(Reporter)

Comment 3

12 years ago
This was seen in 1.0.3.
You need to log in before you can comment on or make changes to this bug.