Bug 111676 - Tropico 6 apitrace throws error into logs
Summary: Tropico 6 apitrace throws error into logs
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/Iris (show other bugs)
Version: git
Hardware: Other All
: not set not set
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-12 12:38 UTC by Denis
Modified: 2019-09-25 18:47 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Denis 2019-09-12 12:38:36 UTC
Hi, during testing this issue => https://bugs.freedesktop.org/show_bug.cgi?id=111631 I found out that iris throws exception into logs (exactly in the end of the apitrace)



/usr/bin/glretrace+0x25fa21
/usr/lib/libpthread.so.0+0x13cff
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: unsafe_free+0x72461c: ../src/util/ralloc.c:297
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: unsafe_free+0x7245ee: ../src/util/ralloc.c:292
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: ralloc_free+0x72450f: ../src/util/ralloc.c:262
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: iris_delete_shader_state+0x8d1cad: ../src/gallium/drivers/iris/iris_program.c:2194
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: iris_delete_fs_state+0x8d1d90: ../src/gallium/drivers/iris/iris_program.c:2225
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: cso_delete_fragment_shader+0x13df75: ../src/gallium/auxiliary/cso_cache/cso_context.c:662
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: free_zombie_shaders+0x4969b8: ../src/mesa/state_tracker/st_context.c:397
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: st_context_free_zombie_objects+0x496b0c: ../src/mesa/state_tracker/st_context.c:431
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: st_flush+0x49527a: ../src/mesa/state_tracker/st_cb_flush.c:60
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: st_glFlush+0x495398: ../src/mesa/state_tracker/st_cb_flush.c:100
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: _mesa_flush+0x1df957: ../src/mesa/main/context.c:1886
/home/den/mesa64/mesa-git-09.09/lib/dri//iris_dri.so: _mesa_Flush+0x1dfadf: ../src/mesa/main/context.c:1924
/usr/bin/glretrace+0xe467d
/usr/bin/glretrace+0x5d528
/usr/bin/glretrace+0x5fead
/usr/bin/glretrace+0x57f20
/usr/lib/libc.so.6: __libc_start_main+0xf2
/usr/bin/glretrace: _start+0x2d
?
apitrace: info: taking default action for signal 11
Comment 1 Lionel Landwerlin 2019-09-12 12:45:07 UTC
Please give it a go under valgrind, hopefully you can find a lead to what looks like a memory corruption.
Comment 2 Sergii Romantsov 2019-09-12 12:47:31 UTC
Solution:
https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1948
Comment 3 Denis 2019-09-12 13:24:21 UTC
hi Lionel, thanks, will keep in mind this option. For now I checked patch from Sergey - and it fixed this issue. Apitrace finished successfully.


3429946: message: api performance issue 1415: Recompiling fragment shader for program GLSL2840: 
3429946: message: api performance issue 1416:   number of color buffers 1->0
Rendered 1447 frames in 327.109 secs, average of 4.4236 fps
Comment 4 GitLab Migration User 2019-09-25 18:47:55 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1366.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.