Comments (7)
Good question. It should be in this week's release, watch for version 1.72.0. It should happen sometime this week or at the beginning of next week.
from semgrep.
Thank you for reporting this, it's definitely undesired behavior.
The problem goes away if I add a trailing newline character so it could be a simple parsing bug but it doesn't explain the error messages about memory:
Error while running rules:
You are seeing this because the engine was killed.
The most common reason this happens is because it used too much memory.
If your repo is large (~10k files or more), you have three options:
1. Increase the amount of memory available to semgrep
2. Reduce the number of jobs semgrep runs with via `-j <jobs>`. We
recommend using 1 job if you are running out of memory.
3. Scan the repo in parts (contact us for help)
Otherwise, it is likely that semgrep is hitting the limit on only some
files. In this case, you can try to set the limit on the amount of memory
semgrep can use on each file with `--max-memory <memory>`. We recommend
lowering this to a limit 70% of the available memory. For CI runs with
interfile analysis, the default max-memory is 5000MB. Without, the default
is unlimited.
The last thing you can try if none of these work is to raise the stack
limit with `ulimit -s <limit>`.
If you have tried all these steps and still are seeing this error, please
contact us.
Error: semgrep-core exited with unexpected output
INFO:semgrep_core:Existing stack limits: Soft: 10485760, Hard: 10485760
INFO:semgrep_core:Trying to set soft limit to 1048576000
INFO:semgrep_core:Failed to set stack limit to 1048576000, 10485760. Trying again.
INFO:semgrep_core:Trying to set soft limit to 1000000000
INFO:semgrep_core:Failed to set stack limit to 1000000000, 10485760. Trying again.
INFO:semgrep_core:Trying to set soft limit to 512000000
INFO:semgrep_core:Failed to set stack limit to 512000000, 10485760. Trying again.
INFO:semgrep_core:Trying to set soft limit to 104857600
INFO:semgrep_core:Failed to set stack limit to 104857600, 10485760. Trying again.
INFO:semgrep_core:Trying to set soft limit to 52428800
INFO:semgrep_core:Failed to set stack limit to 52428800, 10485760. Trying again.
INFO:semgrep_core:Trying to set soft limit to 51200000
INFO:semgrep_core:Failed to set stack limit to 51200000, 10485760. Trying again.
INFO:semgrep_core:Trying to set soft limit to 10485760
INFO:semgrep_core:Successfully set stack limit to 10485760, 10485760
!!!This is a proprietary extension of semgrep.!!!
!!!You should not call directly this program.!!!
from semgrep.
Hello , @mjambon and thanks for your feedback , would this be fixed soon ?
from semgrep.
Hopefully within the next month. Ping us if this is blocking you.
from semgrep.
Hello @mjambon yes this issue is blocking me , can it be fixed in the upcoming days ? Thank you so much and happy weekend
from semgrep.
@mustafanaa I'll work on it next week if there's no last-minute emergency. 🤞
from semgrep.
Thanks , will be this on the next release ? When can i start testing it
from semgrep.
Related Issues (20)
- "taint_assume_safe_functions: true" dosen't work while setting "control: true" in pattern-sources filed HOT 1
- Support for non-file configuration (and tests, maybe) HOT 4
- Failing to parse valid Java 21 syntax: case when statement
- Semgrep Pro language server seems to force downloading rules online HOT 4
- Request for ppc64le Support for Semgrep Binary and Docker Image HOT 1
- Join Mode - TypeError: unhashable type: 'list'
- Gitlab SAST report is not generated when there is error running Semgrep in >=1.64.0 HOT 2
- Ruby metavariable-pattern failed because $KEY does not bind to a sub-program HOT 1
- Python's class pattern of structural pattern matching is treated as class instantiation
- TypeScript non-null assertion operator `!` parsed with wrong precedence HOT 1
- semgrep ci [targets] is not supported
- Engine(PartialParsing) error when parsing Dockerfile with square brackets ([ ])
- --junit-xml-output option not working
- Users can't start with an underscore (`_`) in Dockerfiles
- [PHP] unimplemented RFC: Allow a trailing comma in function calls
- Long list seems to cause stack overflow in language server, but not in CLI
- Custom file name matching for Dockerfiles
- [Feature Request] Support for Filtering Findings from the CLI
- [Python] Parse error for Python 3.11 feature
- Semgrep returns status code 0 when an invalid rule is provided
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from semgrep.