[SERVER-19558] ScopeCache doesn't see cleanup in shutdownServer Created: 23/Jul/15  Updated: 30/Jan/16  Resolved: 23/Jul/15

Status: Closed
Project: Core Server
Component/s: JavaScript
Affects Version/s: 3.1.7
Fix Version/s: 3.1.7

Type: Bug Priority: Major - P3
Reporter: Mira Carey Assignee: Mira Carey
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Platform 7 08/10/15
Participants:
Linked BF Score: 0

 Description   

Migrating to SpiderMonkey had a necessary but unfortunate implementation side effect of adding a thread in between the the scope cache and the actual scopes it caches. We added that thread because SpiderMonkey strictly requires that runtime's only be accessed by one thread across their entire lifetime.

It seems that LSAN can't track reachability across this thread, which is a problem because the scope cache is global. Our lack of clean shutdown prevents the cache from ever being cleaned up, which then looks to LSAN like a leak.

Let's fix that by dropping the cache in shutdownServer



 Comments   
Comment by Githook User [ 28/Jul/15 ]

Author:

{u'username': u'hanumantmk', u'name': u'Jason Carey', u'email': u'jcarey@argv.me'}

Message: SERVER-19558 drop scopeCache in shutdownServer

makes leak sanitizer happy
Branch: master
https://github.com/mongodb/mongo/commit/9c5c717c7af9f1ebbc788d11ff54f8bd83cd0b67

Comment by Githook User [ 23/Jul/15 ]

Author:

{u'username': u'hanumantmk', u'name': u'Jason Carey', u'email': u'jcarey@argv.me'}

Message: SERVER-19558 drop scopeCache in shutdownServer

makes leak sanitizer happy
Branch: master
https://github.com/mongodb/mongo/commit/9c5c717c7af9f1ebbc788d11ff54f8bd83cd0b67

Generated at Thu Feb 08 03:51:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.