Test failing ends up crashing the Glmark2 application

Bug #1031378 reported by Alvaro Moran
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Based on the question #204337 (https://answers.launchpad.net/glmark2/+question/204337).

On some Android devices I have been eble to pop up the Glmark2 app and run the complete benchmark list, having the score at the end.
The issue is that some of the devices fail to render one of the tests (eg.: terrain), but instead of reporting it and continuing with the following benchmarks, it silently ends the run and goes back to the main screen.

After investigation, it appears to be a bug.

Revision history for this message
Alvaro Moran (dirac3000) wrote :

Attached logcat appearing around the test.

Revision history for this message
Alexandros Frantzis (afrantzis) wrote :

libusc is the shader compiler library. The crash is happening in that library and therefore this is almost certainly a driver issue. I am going to mark this as invalid for glmark2. Feel free to reopen if you have additional information suggesting otherwise.

As a workaround, you may to create your own benchmark list, excluding the benchmark that causes this error (it seems to be "terrain"). Note that in trunk (and the upcoming 2012.08 release) you have the ability to save/load benchmark lists from the GUI. You can find the default benchmarks here: https://bazaar.launchpad.net/~glmark2-dev/glmark2/trunk/view/head:/src/default-benchmarks.h

Changed in glmark2:
status: New → Invalid
Revision history for this message
Alvaro Moran (dirac3000) wrote :

Well, I still think something should be done about this. Even if the bug causing the test to fail is elsewhere (eg: in the driver), I think this shouldn't prevent the other tests in the list to run and give a score in the end, perhaps saying which test failed.

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

Other bug subscribers