There's no need to allocate a completely new nsCString when all we want to do is parse a character string into an integer. We can allocate a dependent string instead, which will avoid some memory churn.
We should really be parsing the `const char*` directly, but one step at a time...
Attachment #8956933 - Flags: review?(michal.novotny)
Attachment #8956933 - Flags: review?(michal.novotny) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/0f64845d179b don't allocate nsCStrings when doing integer parsing; r=michal
You need to log in before you can comment on or make changes to this bug.