[CR] Memory Limit Error

Follow

Issue

You encountered the following error when running a scan with Card Recon:

"Some data may be inaccessible: Memory limit of [xxxx] bytes reached, needed [xxxx] more"

Reason

This error occurs when the amount of data that is parsed and decoded by the Card Recon scanning engine reaches the default 1 GB memory limit. This default memory limit is typically sufficient for the Card Recon process unless scanning unusually large files or archives (e.g. ZIP files).

Resolution

This issue can be resolved by increasing the memory limit that can be used by the scanning engine. To increase the memory limit:

  1. Launch the Card Recon GUI.
  2. Configure Card Recon through the dashboard (e.g. select the Targets, Data Types, resource usage...). See Card Recon Graphic User Interface for more information.
  3. Create a Card Recon configuration file (e.g. cardrecon.cfg) by clicking on Tools Save search configuration.
    card-recon-tools-saveconfig.png
  4. Without exiting the Card Recon GUI, open the configuration file (e.g. cardrecon.cfg) with a text editor (e.g. WordPad or Notepad++).
  5. Add the following lines towards the end of the cardrecon.cfg configuration file:
    <recon>
    ...
    <upload>true</upload>
    <engine>
    <decode>
    <totalmem>[total memory]</totalmem>
    <mem>[memory]</mem>
    </decode
    </engine>
    </recon>
    Where:
    - [total memory] is the total memory (in bytes) that the scanning engine can utilize for parsing and decoding data across all data streams
    [memory] is the total memory (in bytes) that the scanning engine can utilize for parsing and decoding data per data stream
  6. Save the Card Recon configuration file in the text editor and reload it in the Card Recon GUI by clicking on Tools Load search configuration.
    card-recon-tools-loadconfig.png
  7. Start scanning your Targets with Card Recon.

Example Card Recon Configuration File

<recon>
...
<upload>true</upload>
<engine>
<decode>
<totalmem>8589934592</totalmem>
<mem>2147483648</mem>
</decode
</engine>
</recon>

 

All information contained in this article is accurate on the stated publication or last modification date.

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.