Project

General

Profile

Bug #3910

datasets: for type string the memcap isn't applied to the string data

Added by Victor Julien 10 months ago. Updated 17 days ago.

Status:
Assigned
Priority:
Normal
Target version:
Affected Versions:
Effort:
Difficulty:
Label:

Description

The memcap checking and tracking only tracks the fixed size THashData and StringType, but not the length of the data in StringType::ptr.

#1

Updated by Victor Julien 10 months ago

  • Description updated (diff)
#2

Updated by Victor Julien 9 months ago

  • Status changed from New to Assigned
  • Assignee set to Shivani Bhardwaj
  • Target version set to 7.0rc1
#3

Updated by Victor Julien 17 days ago

One issue is how to deal with upgrades. If suddenly more data is accounted in the memcap, existing setups might suddenly hit the memcap after upgrading.

#4

Updated by Jason Ish 17 days ago

I don't see a nice way about it. Does this mostly refer to setting of a memcap in a rule where the user will have a harder time changing it assuming they are getting it from a 3rd source?

Could we define a dataset name under datasets before loading the rule that defines that dataset, the memcap set there would serve as an override?

Also available in: Atom PDF