MGD (version 3.5.1.19fd655b) freezes on me when I try to view a frame capture. I can capture the frame, or load a previously saved capture, but when I click on any of the glDrawElements calls in the Trace Outline, MGD freezes. I captured the trace on a non-rooted Galaxy S6 on Android 5.0.2.
Hi cegbert,
Thanks for your report.
What operating system are you running Mali Graphics Debugger on? I gave it a quick go on Windows 7 64-bit and Ubuntu 15.10 64-bit and I coudn't reproduce it...
What is the size of the trace file? Increasing available memory may help, as described in the User Guide:
Increasing the amount of memory made available to the application will increase the maximum trace size that may be accommodated.
To do this, locate the mgd.ini file within the application installation and open it with a text editor.
Find the Java Virtual Machine (JVM) argument starting with ‘-Xmx...’.
The number that follows the argument defines the maximum amount of memory that the application will claim when running, with a trailing ‘m’ for megabytes.
This number can be increased to match the capabilities of your system.
Please note the format for the argument and ensure that your modifications follow the same format exactly (i.e. no spaces, trailing lower-case ‘m’).
The number you enter must be a multiple of 4.
Cheers,
Jacek
I'm on Win10 64 bit, using the 64 bit version of MGD. The trace file is about 13 MB. I increased the -Xmx value from 2000m to 8000m. It doesn't entirely freeze now, but clicking on a glDrawElements causes it to become unresponsive for a few minutes, after which I see the framebuffer in the Framebuffers window, but a message box opens up that has a low memory warning (81 MB remain). I can click around a little bit, but if I go to a new glDrawElements I get more low memory message boxes. mgd.exe is using 1,101,0216K of Private Bytes with a working set of 966,772K, and I have 5.6 GB of free memory. Increasing the -Xmx value doesn't seem to change anything.
Thanks for providing the details. Unfortunately I couldn't reproduce the issue on Windows 10 64-bit.
Is there any chance you can send us the trace file so we can use it to reproduce the problem internally?
Sure. Let me know how to send it.
Great! Please send the trace file to mali-tools-support AT arm DOT com
Thanks for the trace file. Unfortunately I still can't reproduce the problem - Mali Graphics Debugger v3.5.1 seems to be working fine with your trace file on my machine with Windows 10 64-bit.
I've raised an internal ticket to track this issue and I'll ask someone to have more detailed look at it.
Regards,
I tried on a different machine with Windows 8.1 and I'm seeing similar results.
Sorry to hear that.
The graphics engine can use hardware to render UI, so could you please let us know what graphics card you are using? Are the latest drivers installed?
Also, please try to add -Dprism.order=sw to mgd.ini to use software renderer - it may help if there are issues with the graphics card drivers.
To make sure Mali Graphics Debugger uses the options set in mgd.ini please open the application and navigate to:
Help -> About Mali Graphics Debugger -> Installation Details button -> Configuration tab
and verify that you can locate the newly set options there.