My patch introduces a new Warnings mechanism for JS. If this works
nicely, I'd like to extend this to C++.
Basically, whenever you encounter a situation that should never happen
in production but that is not quite fatal enough to warrant a crash, we
call (from the top of my head)
can we keep the
snarkfest version running please until this is resolved?
My main concern was because I inferred from the previous post that
deprecation of snarkfest was scheduled on a timeline basis.
Can we instead schedule on a when-its-ready basis, please?
yes- we are not doing
What exactly are you trying to do?
On 05/06/15 09:22, 罗勇刚(Yonggang Luo) wrote:
--
David Rajchenbach-Teller, PhD
Performance Team, Mozilla
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Hi Dan,
Thanks for the explanation. At this point, I really believe that Mozilla
needs to provide a link pointing to this explanation as well as a link to a
ticket with Oracle. The issue that makes makes me so frustrated (and I'm
guessing others like me who've read this thread) is the lack of
On 2015/06/04 21:38, Robert O'Callahan wrote:
Usually I use NS_WARNING to mean something weird and unexpected is
happening, e.g. a bug in Web page code, but not necessarily a browser bug.
Sometimes I get useful hints from NS_WARNING spew leading up to a serious
failure, but for those usages
You need to look further up the stack. jemalloc_crash is not an
interesting stack frame.
- Kyle
On Fri, Jun 5, 2015 at 8:05 AM, Meenakshi Shankar hifromme...@gmail.com
wrote:
Hi,
We are using Firefox SDKS for our FF extension (libs generated after
compiling Firefox 39 beta 2 source using
6 matches
Mail list logo
