Scalene error: received signal SIGSEGV
See original GitHub issueGetting Scalene error: received signal SIGSEGV
when trying to profile a python program.
I believe one of the imports at the top of my code breaks the profiler.
test.py:
#!/usr/bin/env python
# coding: utf-8
import obspy
profiling
scalene test.py
output: Scalene error: received signal SIGSEGV
Desktop:
- OS: macOS-10.16-x86_64
Issue Analytics
- State:
- Created 3 years ago
- Comments:14 (8 by maintainers)
Top Results From Across the Web
Resolve error "Program received signal SIGSEGV ...
Issue and Resolution User receives this error when trying to retrieve file: Program received signal SIGSEGV, Segmentation fault. After analysing the logs and ......
Read more >Error: Program received signal SIGSEGV: Segmentation fault
Dear, There is a problem like this when I try to run CAMx v7.00 Program received signal SIGSEGV: Segmentation fault - invalid memory...
Read more >Workaround to successfully profile python script using ...
I received a two line error and was exited from python in a normal way. Error getting real path: 2 Scalene error: received...
Read more >Segmentation Fault (SIGSEGV) vs Bus Error (SIGBUS)
1) Segmentation Fault (also known as SIGSEGV and is usually signal 11) occur when the program tries to write/read outside the memory ...
Read more >scalene
Fail installing scalene in docker container FROM python:3.10-alpine3.16 with RUN ... Getting Scalene error: received signal SIGSEGV when trying to profile a ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For reference, this issue has been posted on the PyTorch repo. As it’s not a Scalene bug, I’m closing the issue here.
Documented in
README.md
with https://github.com/plasma-umass/scalene/commit/6636d95d7ea9a16adedaedbd4ff0926374798f2b.