totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.

[El jinete sin cabeza]

https://gitlab.gnome.org/GNOME/totem/issues/297 (Not GNOME)

---

I'm not sure, but this happened after updating to gstreamer 1.15.1, I have problems when I maximize totem.

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: totem 3.30.0-4ubuntu1
Uname: Linux 4.20.7-042007-generic x86_64
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
AssertionMessage: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 7 18:40:29 2019
ExecutablePath: /usr/bin/totem
InstallationDate: Installed on 2018-12-02 (68 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcCmdline: /usr/bin/totem --gapplication-service
Signal: 6
SourcePackage: totem
StacktraceTop:
 __assert_fail_base (fmt=0x7ff31939be23 <error: No se puede acceder a la memoria en la dirección 0x7ff31939be23>, assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=<optimized out>) at assert.c:92
 __GI___assert_fail (assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=0x7ff312a56938 "__gen_uint") at assert.c:101
 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
Title: totem assert failure: totem: src/intel/genxml/gen9_pack.h:72: __gen_uint: La declaración `v <= max' no se cumple.
UpgradeStatus: Upgraded to disco on 2018-12-02 (67 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 __assert_fail_base (fmt=0x7ff31939be23 <error: Cannot access memory at address 0x7ff31939be23>, assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=<optimized out>) at assert.c:92
 __GI___assert_fail (assertion=assertion@entry=0x7ff312a5416c "v <= max", file=file@entry=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=line@entry=72, function=function@entry=0x7ff312a56938 <__PRETTY_FUNCTION__.50862> "__gen_uint") at assert.c:101
 __gen_uint (v=<optimized out>, start=16, end=31) at src/intel/genxml/gen9_pack.h:64
 __gen_uint (end=<optimized out>, start=<optimized out>, v=<optimized out>) at src/intel/genxml/gen9_pack.h:64
 GEN9_SCISSOR_RECT_pack (data=0x0, values=<synthetic pointer>, dst=0x7ff2a2e275a0) at src/intel/genxml/gen9_pack.h:649

[El jinete sin cabeza (ejsc)]

https://gitlab.gnome.org/GNOME/totem/issues/297#note_432608

Bastien Nocera:
"Looks like a crash inside the application side intel driver inside Mesa. It's going to be a driver problem rather than something that totem can deal with."

[El jinete sin cabeza (ejsc)]

Open bug in launchpad.net:

https://bugs.launchpad.net/bugs/1815236

Package: mesa 18.3.2-1ubuntu1
Package: totem 3.30.0-4ubuntu1

"I'm not sure, but this happened after updating to gstreamer 1.15.1"

BackTrace:
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
        set = {__val = {0, 94498293496560, 94498277471360, 140682175812304, 140733120872448, 94498293496560, 94498293496560, 94498293496560, 94498293496560, 94498293496653, 94498293496660, 94498293496560, 94498293496660, 0, 0, 0}}
        pid = <optimized out>
        tid = <optimized out>
        ret = <optimized out>
#1 0x00007ff31f173535 in __GI_abort () at abort.c:79
        save_stage = 1
        act = {__sigaction_handler = {sa_handler = 0x55f219373af0, sa_sigaction = 0x55f219373af0}, sa_mask = {__val = {0, 140682177240128, 4294967295, 0, 0, 0, 140730987235576, 21474836480, 140730987235424, 140682076995107, 140682076995107, 0, 7607704802042790912, 140682177002746, 0, 140682076995107}}, sa_flags = 312829004, sa_restorer = 0x7ff312a5416c}
        sigs = {__val = {32, 0 <repeats 15 times>}}
#2 0x00007ff31f17340f in __assert_fail_base (fmt=0x7ff31939be23 <error: Cannot access memory at address 0x7ff31939be23>, assertion=0x7ff312a5416c "v <= max", file=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=72, function=<optimized out>) at assert.c:92
        str = 0x55f219373af0 "\260\341;\031\362U"
        total = 4096
#3 0x00007ff31f183142 in __GI___assert_fail (assertion=assertion@entry=0x7ff312a5416c "v <= max", file=file@entry=0x7ff312a5644c "src/intel/genxml/gen9_pack.h", line=line@entry=72, function=function@entry=0x7ff312a56938 <__PRETTY_FUNCTION__.50862> "__gen_uint") at assert.c:101
No locals.
#4 0x00007ff3127baffc in __gen_uint (v=<optimized out>, start=16, end=31) at src/intel/genxml/gen9_pack.h:64
        max = <optimized out>
        width = <optimized out>
        width = <optimized out>
        __PRETTY_FUNCTION__ = "__gen_uint"
        max = <optimized out>
#5 __gen_uint (end=<optimized out>, start=<optimized out>, v=<optimized out>) at src/intel/genxml/gen9_pack.h:64
        width = <optimized out>
        width = <optimized out>
        __PRETTY_FUNCTION__ = "__gen_uint"
        max = <optimized out>
#6 GEN9_SCISSOR_RECT_pack (data=0x0, values=<synthetic pointer>, dst=0x7ff2a2e275a0) at src/intel/genxml/gen9_pack.h:649
        dw = 0x7ff2a2e275a0
        dw = <optimized out>
#7 gen9_upload_scissor_state (brw=0x55f21842b480) at ../src/mesa/drivers/dri/i965/genX_state_upload.c:2471
        i = 0
        ctx = 0x55f21842b480
        flip_y = true
        scissor = <optimized out>
        scissor_state_offset = 1440
        fb_width = <optimized out>
        fb_height = 385
        scissor_map = 0x7ff2a2e275a0
        viewport_count = 1
#8 0x00007ff312359a91 in check_and_emit_atom (atom=0x55f218442608, state=<synthetic pointer>, brw=0x55f21842b480) at ../src/mesa/drivers/dri/i965/brw_state_upload.c:496
No locals.
#9 brw_upload_pipeline_state (pipeline=BRW_RENDER_PIPELINE, brw=0x55f21842b480) at ../src/mesa/drivers/dri/i965/brw_state_upload.c:615
        atom = 0x55f218442608
        devinfo = <optimized out>
        ctx = 0x55f21842b480
   ...

[Chris Wilson (ickle)]

*** Bug 109595 has been marked as a duplicate of this bug. ***

[Lionel-g-landwerlin (lionel-g-landwerlin)]

I managed to reproduce only once, but then lost my session.

Is there a way to reproduce this reliably?

[El jinete sin cabeza (ejsc)]

(In reply to Lionel Landwerlin from comment #2)
> I managed to reproduce only once, but then lost my session.

It happens the same to me. I must press "ctrl + alt + f3" a terminal opens, and restart Ubuntu.

> Is there a way to reproduce this reliably?

I can always reproduce this bug. I open the movie through 'nautilus'. Totem opens, and I watch the movie. But if 'maximizo' totem freezes the desktop.

[Lionel-g-landwerlin (lionel-g-landwerlin)]

(In reply to El jinete sin cabeza from comment #3)
> (In reply to Lionel Landwerlin from comment #2)
> > I managed to reproduce only once, but then lost my session.
>
> It happens the same to me. I must press "ctrl + alt + f3" a terminal opens,
> and restart Ubuntu.
>
>
> > Is there a way to reproduce this reliably?
>
> I can always reproduce this bug. I open the movie through 'nautilus'. Totem
> opens, and I watch the movie. But if 'maximizo' totem freezes the desktop.

How do you trigger maximize? Double click on the title bar or Alt-ArrowUp or something else?

[El jinete sin cabeza (ejsc)]

I do not know if the error is random. But after the update that I made today. The error does not happen.

[El jinete sin cabeza (ejsc)]

Created attachment 143360
Screenshot when it fails. Totem is left full screen

It happened to me again. By leaving the movie full screen.

[Denys-kostin (denys-kostin)]

Hi, could you please provide an example of movie which reproduces the issue? In my case I simply using "mp4 sample" video with rabbit, it could be not enough for reproducing the issue.

[El jinete sin cabeza (ejsc)]

(In reply to Denis from comment #7)
> Hi, could you please provide an example of movie which reproduces the issue?
> In my case I simply using "mp4 sample" video with rabbit, it could be not
> enough for reproducing the issue.

https://pirateproxy.bet/torrent/9496094/Akira_(1988)_-_25th_Anniversary_Edition_[BD_1080p]

[Kenxeth (kenxeth)]

Setting back to Drivers/DRI/i965, which is the driver you are using.

[Denys-kostin (denys-kostin)]

hey guys, we spent lot of time for investigation of this issue, and found out that this patch fixes everything:
>https://gitlab.freedesktop.org/mesa/mesa/merge_requests/252

Short bug description:
1. Issue is reproducible only on Wayland session, we couldn't reproduce it on X
2. There are actually 3 issues in total:

1) Assertion error in player
2) strange system "hang" which leads to only one way - rebooting
3) weird "extra" artifacts in the player during resizing window.

3. We managed to bisect 2) problem, and it leaded us to this commit:
__________
a9fb331ea7d1a78936ea8d8385e44cfd66f835c1 is the first bad commit
Author: Juan A. Suarez Romero <email address hidden>
Date: Wed Jun 6 10:13:05 2018 +0000

    wayland/egl: update surface size on window resize

 CC: Daniel Stone <email address hidden>
    CC: <email address hidden>
    Reviewed-by: Daniel Stone <email address hidden>
__________
So that's how we found that merge_request. As I said, for me it fixed all 3 issues, but would be great if somebody could also re-test it.

[Daniel van Vugt (vanvugt)]

No problem. There's a working patch (apparently) in the Mesa bug:

https://bugs.freedesktop.org/show_bug.cgi?id=109594

[Qamonstergl (qamonstergl)]

Hi guys
The fix was merged to master.
I've rechecked the issues.
Main issue was fixed - the system doesn't hang at resizing of the totem-player.
Also, during the testing, I found a patch (https://patchwork.freedesktop.org/patch/267292/) which fixes the issue with crash of the totem-app.

[Qamonstergl (qamonstergl)]

will close this issue when one more patch appears in master

[Baker-dylan-c (baker-dylan-c)]

The mentioned patch has landed in master and 19.0 (presumably it is or will be in 18.3 shortly), is this okay to close?

[Qamonstergl (qamonstergl)]

The patch was merged to master.
I've performed piglit-test and run check totem-app functionality - all looks good.
I close the card.

[El jinete sin cabeza (ejsc)]

They could pass to [1]mesa_19.0.0~rc7
[1] https://metadata.ftp-master.debian.org/changelogs/main/m/mesa/mesa_19.0.0~rc7-1_changelog

https://bugs.freedesktop.org/show_bug.cgi?id=109535
The error is corrected in master.

[El jinete sin cabeza (ejsc)]

I am looking for if the patch was included before the release of mesa "19.0.0-rc7"

[Launchpad Janitor (janitor)]

This bug was fixed in the package mesa - 19.0.0-1ubuntu1

---------------
mesa (19.0.0-1ubuntu1) disco; urgency=medium

  * Merge from Debian. (LP: #1818516)
  * revert-set-full-thread-affinity.diff: Fix qemu crash. (LP: #1815889)

 -- Timo Aaltonen <email address hidden> Thu, 14 Mar 2019 18:48:18 +0200