Bug 218188 - www/firefox + SNDIO cannot reach 60fps without sndiod running
Summary: www/firefox + SNDIO cannot reach 60fps without sndiod running
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-gecko (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-28 16:10 UTC by Jan Beich
Modified: 2023-04-23 20:03 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (gecko)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Beich freebsd_committer freebsd_triage 2017-03-28 16:10:06 UTC 

    


    


      



        
          Comment 1
        

        
          Jan Beich

        

        
            freebsd_committer
            freebsd_triage
        

        
          2017-03-28 16:12:48 UTC
        

      






1. Build www/firefox with SNDIO selected
2. Don't launch sndiod
3. Open Youtube
4. Find a 60fps video
5. Play it
6. Notice the video is choppy
7. Toggle layers.acceleration.draw-fps in about:config
8. Notice FPS is capped at ~30fps

    


    


      



        
          Comment 2
        

        
          Jan Beich

        

        
            freebsd_committer
            freebsd_triage
        

        
          2017-03-28 16:17:34 UTC
        

      






Hmm, the issue appears to be specific to HTML5 video. Wasm + WebGL demos reach 60fps just fine.

    


    


      



        
          Comment 3
        

        
          Walter Schwarzenfeld

        

        
        

        
          2019-08-03 11:58:48 UTC
        

      






Is this still relevant?

    


    


      



        
          Comment 4
        

        
          Tobias Kortkamp

        

        
            freebsd_committer
            freebsd_triage
        

        
          2019-08-03 12:03:11 UTC
        

      






(In reply to w.schwarzenfeld from comment #3)
> Is this still relevant?

Yes.