don't use nspr allocator for js threads for better ASAN

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.4.10, 3.6.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v3.4
    • Platforms 2017-10-02
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      js threads can be freed in different threads than where they were created, and this breaks our ASAN-specific pointer tracker. So, if we just use the regular allocator for the threads, as opposed to the nspr allocator, then we won't try to track them.

            Assignee:
            Gabriel Russell (Inactive)
            Reporter:
            Gabriel Russell (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: