Heap corrupted with ofGLRenderer
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- computer-graphics, desktop
Research direction
Reproduce the issue on Windows using gflags full page heap and the provided ofApp example with a dummy h.png. Start by tracing ofGLRenderer::draw, especially the ofFbo texture alpha-mask and subsequent image draw; compare behavior with settings.setGLVersion(3, 2). Done means the reproducer no longer corrupts the heap or crashes under page heap verification.
Written by the indexing model from the issue text.
Description
The ofGLRenderer seems to corrupt the heap in some cases.
It gets reproducable if some heap fail-safing software is used. I was able to reproduce it with gflags on Windows. Use this to enable full page heap verification for the built executable, in my case crash_debug.exe
gflags.exe /p /enable crash_debug.exe /full
Here is the code that reproduces this if page heap is activated. Just use a dummy file for h.png
int main()
{
ofGLWindowSettings settings;
//uncommenting the following line makes the crash go away as ofGLProgrammableRenderer is used
// settings.setGLVersion(3, 2);
ofCreateWindow(settings);
ofRunApp(new ofApp());
}
void ofApp::setup()
{
}
void ofApp::update()
{
}
void ofApp::draw()
{
ofFbo container;
ofImage maskRight;
ofImage header;
maskRight.load("h.png");
container.allocate(100, 100, GL_RGBA);
container.getTexture().setAlphaMask(maskRight.getTexture());
container.draw(0, 0);
header.load("h.png");
header.draw(0, 0);
}
This crashes in ofGLRenderer::draw every time now, so there really seems to be something trashing the heap. Without the enabled gflags page heap it will crash randomly after a few minutes or days.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from openframeworks/openFrameworks
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
openframeworks/openFrameworks#6532 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
openframeworks/openFrameworks#6380 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
openframeworks/openFrameworks#4817 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
openframeworks/openFrameworks#8553 · 1 comment ·
-
projectGenerator (vs): addon .c sources compiled as C++, causing unresolved externals (ofxLua: 55) Open
openframeworks/openFrameworks#8546 · 1 assignee ·
All issues in openframeworks/openFrameworks
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·