Closed floere closed 9 years ago
Copy-On-Write, not a :cow: ;)
Can you reproduce it locally and do you have a debug build of Ruby? If so, it's probably easiest to do some heap analysis? (e.g. with Instruments.app's Heapshot instrument.)
That's probably possible :) And I keep forgetting about Instrument.app.
This is not an actual problem we have (it's ok to go over the memory limit for a short time), just something I am wondering about.
Ah ok, well, there was your half-yearly reminder about Instruments.app ;)
I've already forgotten about it again ;)
Sorry, won’t remind you for another 181.5 days!
@alloy Let's see how Ruby 2.2 fares. Maybe it won't do a COW when just accessing a hash.
@alloy MUST REMEMBAH
lol. COW.
C'est réparé!
Because we fork for sending the stats to status.cocoapods.org, the memory spikes.
Why? Are we writing when we do so, triggering a COW?