App crash: corrupted size vs. prev_size in fastbins

SGaist

Hi,

Did you try to check system logs to see if there was something wrong going on ?
What about memory used by your application ?

LeBeef

Hi @SGaist,

fortunately we are logging all the pc resources, but there was nothing unusual during the crash and nothing unusual in syslog. Another error I saw around the crash is this:

[AVHWFramesContext @ 0x7f7b28051180] Failed to sync surface 0x3f: 1 (operation failed).

SGaist

What about dmesg ?

LeBeef

@SGaist said in App crash: corrupted size vs. prev_size in fastbins:

dmesg

Unfortunately no messages related to the crashes.

SGaist

Strange...
What is your video hardware ?

LeBeef

@SGaist We have our app running on two different systems. One has a Nvidia GPU and one has intel graphics. It happens only on the one with intel graphics. Here are the details:

        *-display
             description: VGA compatible controller
             product: Alder Lake-P Integrated Graphics Controller
             vendor: Intel Corporation
             physical id: 2
             bus info: pci@0000:00:02.0
             logical name: /dev/fb0
             version: 0c
             width: 64 bits
             clock: 33MHz
             capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
             configuration: depth=32 driver=i915 latency=0 mode=1920x1080 resolution=1920,1080 visual=truecolor xres=1920 yres=1080
             resources: iomemory:600-5ff iomemory:400-3ff irq:165 memory:6000000000-6000ffffff memory:4000000000-400fffffff ioport:3000(size=64) memory:c0000-dffff memory:4010000000-4016ffffff memory:4020000000-40ffffffff

LeBeef

PS: It happens on multiple instances of intel, which playback different video files.

SGaist

Ok, so at least there's some common point of failure.

Which backend are you using ?

LeBeef

@SGaist Since I did not set anything with an ENV var I guess it is using ffmpeg right?

SGaist

Since you are using 6.7, that should be the default yes.

You can check that by setting the QT_DEBUG_PLUGINS environment variable to 1 in the terminal where you start your application.