Skip navigation.
 
mlRe: Crash in CGDisplayCurrentMode()
FROM : Nigel Pearson
DATE : Tue Apr 19 01:08:22 2005

Hi Tim. Thanks for the response.

>  My guess would be that the display mode dictionary
> is getting deallocated and you are hitting a zombie.


   Possible, but why would the CoreGraphics library code be
deallocating the dictionary that it is meant to return to me?

(check the stack trace - it is crashing _in_ the CGDisplayCurrentMode()
call)


   The really freaky thing? I tried running it today with
MallocStackLogging=1 set in the environment. No crash
(though it was a lot slower). So I try it without that.
Also no crash. F*^&#ng non-deterministic code :-(


...
> Note, it isn't clear to me that you are _ever_ supposed
> to release the result of CGDisplayCurrentMode.


   Correct, it is a reference to a CG private data structure.


--
Nigel Pearson, <email_removed> | "Gentlemen,
Telstra BI&D, Sydney, Australia      |  you can't fight in here
Office: 8255 4222    Fax:  8255 3153  |  - this is the war room!"
Mobile: 0408 664435  Home: 9792 6998  |      Dr Strangelove

Related mailsAuthorDate
mlCrash in CGDisplayCurrentMode() Nigel Pearson Apr 18, 04:22
mlRe: Crash in CGDisplayCurrentMode() Timothy J.Wood Apr 18, 18:20
mlRe: Crash in CGDisplayCurrentMode() Nigel Pearson Apr 19, 01:08
mlRe: Crash in CGDisplayCurrentMode() Timothy J.Wood Apr 19, 02:33
mlRe: Crash in CGDisplayCurrentMode() Nigel Pearson Apr 28, 08:49