Genesi EfikaMX Support Project

glcompbench doesn't work on Efika MX Smart book

Bug #736811 reported by Jammy Zhou
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Genesi EfikaMX Support Project
New
Undecided
Unassigned

Bug Description

glcompbench is a benchmark for testing the composite performance: https://launchpad.net/glcompbench

When run glcompbench on Efika MX SB, the window is always dark red, but there should be some texture images as expected. And it seems that the application enters endless loop when run with "--benchmark" option.

Revision history for this message
Jammy Zhou (jammy-zhou) wrote :

And if use X image instead of egl image for compositing test (use --no-accel-tfp option), segmentation fault happens for glcompbench when call glTexSubImage2D in CompositeWindowXImage::update_texture_from_pixmap.

Revision history for this message
Jesse Barker (jesse-barker) wrote :

The "--benchmark" option issue has been fixed in glcompbench. It turns out that the timestamp computation was never satisfying the time interval for computing FPS and updating the test iteration. The rest of this issue is still relevant.

Revision history for this message
Matt Sealey (mwsealey) wrote : Re: [Bug 736811] Re: glcompbench doesn't work on Efika MX Smart book

I'm really not sure why it's segfaulting there..

--
Matt Sealey <email address hidden>
Product Development Analyst, Genesi USA, Inc.

On Sat, Mar 19, 2011 at 6:43 AM, Jammy Zhou <email address hidden> wrote:
> And if use X image instead of egl image for compositing test (use --no-
> accel-tfp option), segmentation fault happens for glcompbench when call
> glTexSubImage2D in CompositeWindowXImage::update_texture_from_pixmap.
>
> --
> You received this bug notification because you are subscribed to Genesi
> EfikaMX Support Project.
> https://bugs.launchpad.net/bugs/736811
>
> Title:
>  glcompbench doesn't work on Efika MX Smart book
>

Revision history for this message
Matt Sealey (mwsealey) wrote :

Running the benchmark now I get a blue fadey window which shows we have absolutely terrible performance.

--no-accel-ftp still segfaults but I can't track exactly what is segfaulting or why. Does anyone have any decent gdb data from it? Is it crashing inside the app or the driver?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.