Interestingly, I tried to run Growl using libgmalloc, and it won't even
start:
$ env DYLD_INSERT_LIBRARIES=/usr/lib/libgmalloc.dylib
/Applications/Growl.app/Contents/MacOS/Growl
GuardMalloc[Growl-69473]: Allocations will be placed on 16 byte boundaries.
GuardMalloc[Growl-69473]: - Some buffer overruns may not be noticed.
GuardMalloc[Growl-69473]: - Applications using vector instructions
(e.g., SSE) should work.
GuardMalloc[Growl-69473]: version 24.1
2011-11-20 16:07:14.118 Growl[69473:a0b] <GCDAsyncSocket:
0x7fff0f890f30> now accepting ((null))
2011-11-20 16:07:23.366 Growl[69473:a0b] Setup timer, this should only
happen once
2011-11-20 16:07:23.372 Growl[69473:a0b] Next image check no earlier
than 24 hours from 2011-11-20 04:59:00 +0000
GuardMalloc[Growl-69473]: *** mmap(size=1048576) failed (error code=12)
*** error: can't allocate region securely
*** set a breakpoint in malloc_error_break to debug
GuardMalloc[Growl-69473]: *** malloc_default_scalable_zone() failed to
find 'DefaultMallocZone'
Segmentation fault: 11
On 11/20/11 4:04 PM, Dossy Shiobara wrote:
This time, I ran Growl.app with MallocScribble=1 and
MallocGuardEdges=1, and this is the result:
$ env MallocScribble=1 MallocGuardEdges=1 /Applications
Growl(69281) malloc: protecting edges
Growl(69281) malloc: enabling scribbling to detect mods to free blocks
2011-11-20 13:32:19.785 Growl[69281:b07] <GCDAsyncSocket: 0x10e740540>
now accepting ((null))
2011-11-20 13:32:20.022 Growl[69281:b07] Setup timer, this should only
happen once
2011-11-20 13:32:20.023 Growl[69281:b07] Next image check no earlier
than 24 hours from 2011-11-20 04:59:00 +0000
Growl(69281,0x7fff729c2960) malloc: purgeable zone does not support
guard pages
2011-11-20 14:06:21.784 Growl[69281:b07] Error occurred: Error domain
GrowlNetwork, code 0 (The operation couldn’t be completed. Unknown
binary header Notification-Callback-Context-Type; value PList).
2011-11-20 14:06:21.785 Growl[69281:b07] Failed reading with error:
Error Domain=GrowlNetwork Code=0 "The operation couldn’t be completed.
Unknown binary header Notification-Callback-Context-Type; value PList"
UserInfo=0x7f9ec1e635d0 {NSLocalizedFailureReason=Unknown binary
header Notification-Callback-Context-Type; value PList}
2011-11-20 14:16:36.068 Growl[69281:b07] Deprecated Binding Warning:
'data' binding of class NSImageView is deprecated. You will only see
this warning once.
2011-11-20 14:44:17.557 Growl[69281:b07] Error occurred: Error domain
GrowlNetwork, code 0 (The operation couldn’t be completed. Unknown
binary header Notification-Callback-Context-Type; value PList).
2011-11-20 14:44:17.557 Growl[69281:b07] Failed reading with error:
Error Domain=GrowlNetwork Code=0 "The operation couldn’t be completed.
Unknown binary header Notification-Callback-Context-Type; value PList"
UserInfo=0x7f9ec28aa350 {NSLocalizedFailureReason=Unknown binary
header Notification-Callback-Context-Type; value PList}
2011-11-20 14:44:17.559 Growl[69281:b07] Error occurred: Error domain
GrowlNetwork, code 0 (The operation couldn’t be completed. Unknown
binary header Notification-Callback-Context-Type; value PList).
2011-11-20 14:44:17.560 Growl[69281:b07] Failed reading with error:
Error Domain=GrowlNetwork Code=0 "The operation couldn’t be completed.
Unknown binary header Notification-Callback-Context-Type; value PList"
UserInfo=0x7f9ec299a570 {NSLocalizedFailureReason=Unknown binary
header Notification-Callback-Context-Type; value PList}
And, now, Growl is using 100% CPU of one core, again.
--
Dossy Shiobara | "He realized the fastest way to change
[email protected] | is to laugh at your own folly -- then you
http://panoptic.com/ | can let go and quickly move on." (p. 70)
* WordPress * jQuery * MySQL * Security * Business Continuity *
--
You received this message because you are subscribed to the Google Groups "Growl
Discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/growldiscuss?hl=en.
