I was not planning to put a lot of effort into trying to make printing stack traces low-GC. I agree with Matt that this is an expensive operation anyway and if this happens very often, allocation is probably the least of your problems...
On Thu, Mar 24, 2016 at 1:43 AM, Matt Sicker <[email protected]> wrote: > Do you mean for outputting it? Because obtaining a stack trace is both a > slow operation as well as one requiring an array allocation filled in from > native code, so it already seems like a bad idea for high-throughput > production logging unless you need it. > > On 23 March 2016 at 11:38, Mikael Ståldal <[email protected]> > wrote: > >> Do we have any strategy for allocation free stacktrace formatting >> (PatternLayout %throwable), or is that just non-supported for >> allocation-free configuration? >> >> -- >> [image: MagineTV] >> >> *Mikael Ståldal* >> Senior software developer >> >> *Magine TV* >> [email protected] >> Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com >> >> Privileged and/or Confidential Information may be contained in this >> message. If you are not the addressee indicated in this message >> (or responsible for delivery of the message to such a person), you may >> not copy or deliver this message to anyone. In such case, >> you should destroy this message and kindly notify the sender by reply >> email. >> > > > > -- > Matt Sicker <[email protected]> >
