[SERVER-4068] v8 build sometimes fails sharding/auto2.js, may be due to GC Created: 13/Oct/11  Updated: 11/Jul/16  Resolved: 13/Oct/11

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

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

Operating System: ALL
Participants:

 Description   

reported by Greg:
In the v8 version we're using, it seems like IdleNotification()
doesn't necessarily trigger garbage collection (by design), which
causes auto2.js to fail sometimes on my v8 builds. If we set a global
--expose-gc flag in v8 when creating the engine, there's a built-in
gc() method which forces gc that we can use for testing - the other
IdleNotification we can rename allowGC(). Is there a reason we
shouldn't do this? I've got a patch ready, seems to work.



 Comments   
Comment by auto [ 13/Oct/11 ]

Author:

{u'login': u'agirbal', u'name': u'agirbal', u'email': u'antoine@10gen.com'}

Message: - SERVER-4068: v8 build sometimes fails sharding/auto2.js, may be due to GC
Branch: master
https://github.com/mongodb/mongo/commit/9b12a1c446fc4c21bd833e6b3b1a34d2c15af5bd

Comment by Antoine Girbal [ 13/Oct/11 ]

I think they added a method to force gc directly: LowMemoryNotification();
I'll put that in the gc() method instead of IdleNotification().

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