OpenGL stops working when omxplayer is started
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- raspberry-pi
- Domain
- computer-graphics, operating-systems
Research direction
Reproduce the failure from /opt/vc/src/hello_pi/hello_triangle using the listed tvservice, hello_triangle.bin, and omxplayer commands, comparing current firmware with the 1.20170405 boot files. Investigate the display reconfiguration and GPU firmware behavior; done means the OpenGL cube remains visible after omxplayer starts and stops.
Written by the indexing model from the issue text.
Description
With the current firmware it sometimes happens, that an OpenGL application stops displaying
when omxplayer is started. This happens after the display is reconfigured, while
an OpenGL application runs.
To reproduce this, install Raspbian (tested with 2018-04-18-raspbian-stretch-lite.img).
Enable ssh and increase the gpu memory in /boot/config.txt. Install omxplayer.
Run the following commands over ssh:
cd /opt/vc/src/hello_pi/hello_triangle
make
./hello_triangle.bin &
sleep 1
tvservice -p
sleep 1
killall hello_triangle.bin
sleep 1
./hello_triangle.bin &
sleep 1
omxplayer --layer 1 --win "0,0,860,540" /opt/vc/src/hello_pi/hello_video/test.h264
Normally you would now see the video on top of the cube from hello_triangle, but only the video is visible. Even after the video stops, the cube is still not visible, but the process for hello_triangle still runs.
If you replace the files bootcode.bin, fixup.dat and start.elf on the boot partition with the versions from tag 1.20170405, it works as expected.
This may be related to #903.
- Dominant language
- No language data
- Stars
- 5.6k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 raspberrypi/firmware
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
raspberrypi/firmware#2042 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
raspberrypi/firmware#2040 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
raspberrypi/firmware#2039 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
raspberrypi/firmware#2038 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
raspberrypi/firmware#2037 · 4 comments ·
All issues in raspberrypi/firmware
Similar issues
-
Area:Math p5.js 2.0+
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
processing/p5.js#9197 · 1 comment ·
-
Template: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
BabylonJS/Babylon-Lite#756 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
CyberAgent/psd2svg#360 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
BabylonJS/Babylon.js#18928 ·