Apple CoreGraphics framework logging input data to /tmp

Very very few OSX apps use an alternate allocator so this was probably not noticed. Having written a commercial memory allocator before (for MacOS prior to OSX) the one in OSX is actually quite good for most people. I don&#x27;t know why Mozilla decided they needed jemalloc but maybe it tested better for their usage.<p>Still you would think tracking what&#x27;s written to such a common directory would have been seen by someone at Apple. Firefox isn&#x27;t exactly obscure.

Well every programmer probably made a mistake like that once, twice or more (or just, every programmers makes mistakes tout-court), but imo something like this should have been caught in the pull request&#x2F;code review&#x2F;general testing stage as it concerns a major OS? That being said I obviously have no idea what stages precede an actual release of an OS. Anyone does?

I didn&#x27;t see any logs for firefox, but did see a similar file for Google Earth...<p>&quot;&#x2F;tmp&#x2F;CGLog_Google Earth_7790&quot;<p>full of:<p>7629.0413465 (Google Earth): CGSGetNextEventRecordInternal: 7629.0410916 loc (90.4, 934.0) conn 0x34b5f MouseMoved win 0x4a0 (click 1) 7629.0581342 (Google Earth): CGSGetNextEventRecordInternal: 7629.0578892 loc (84.4, 929.0) conn 0x34b5f MouseMoved win 0x4a0 (click 1) 7629.0750728 (Google Earth): CGSGetNextEventRecordInternal: 7629.0749128 loc (70.4, 918.0) conn 0x34b5f MouseExited win 0x4a0 tArea 0x19494 7629.0750766 (Google Earth): CGSGetNextEventRecordInternal: 7629.0749338 loc (70.4, 918.0) conn 0x34b5f MouseExited win 0x4a0 tArea 0x19493

I&#x27;m using Firefox Developer Edition, and I don&#x27;t see any CGLog_* files in &#x2F;tmp at all. Am I missing something?

another apple 101 screwup.<p>lets hope that this helps encourage them improve their QA process to the point where they at least test real world applications a bit more heavily (or at all). :)