Issue 65 in sarasvati: Unlimited size cache in MemGraphRepository may produce a buffer overflow

0 views
Skip to first unread message

sara...@googlecode.com

unread,
Oct 8, 2010, 5:29:38 AM10/8/10
to sarasvati...@googlegroups.com
Status: New
Owner: ----

New issue 65 by jul...@blass.name: Unlimited size cache in
MemGraphRepository may produce a buffer overflow
http://code.google.com/p/sarasvati/issues/detail?id=65

Using a static instance of cache into MemGraphRepository may produce a
buffer overflow: it might be better to limit the cache size and remove the
oldest MemGraph or find another more suitable mechanism.

sara...@googlecode.com

unread,
Oct 8, 2010, 4:18:08 PM10/8/10
to sarasvati...@googlegroups.com
Updates:
Status: Accepted
Owner: plorenz
Labels: Component-Core-Mem Performance Usability

Comment #1 on issue 65 by plorenz: Unlimited size cache in

MemGraphRepository may produce a buffer overflow
http://code.google.com/p/sarasvati/issues/detail?id=65

I've committed a change that allows a per-engine cache. Let me know if that
will work for you.

http://code.google.com/p/sarasvati/source/detail?r=1178

sara...@googlecode.com

unread,
Oct 13, 2010, 11:34:17 AM10/13/10
to sarasvati...@googlegroups.com
Updates:
Status: Fixed
Labels: Milestone-1.0.4

Comment #2 on issue 65 by plorenz: Unlimited size cache in

MemGraphRepository may produce a buffer overflow
http://code.google.com/p/sarasvati/issues/detail?id=65

I also added a constructor where you can pass in your own
MemGraphRepository.

sara...@googlecode.com

unread,
Oct 17, 2012, 9:37:09 PM10/17/12
to sarasvati...@googlegroups.com
Updates:
Labels: Type-Enhancement

Comment #4 on issue 65 by plor...@gmail.com: Unlimited size cache in
MemGraphRepository may produce a buffer overflow
http://code.google.com/p/sarasvati/issues/detail?id=65

(No comment was entered for this change.)

Reply all
Reply to author
Forward
0 new messages