crash when Battle Field 4 is running

gdb logs

Added attachment:

gdb.txt

added Component::Video: Direct3D / Win32 label

changed milestone to %Bugs paradize

I will take a look but so far I couldn't reproduce a crash when launching a game.

Looking at the backtrace provided, it looks like in the Prepare callback we notice using TestCooperativeLevel() that the device is not in a correct state anymore. The current state of the device is D3DERR_DEVICENOTRESET apparently since a device reset is requested, this is probably incorrect since the game is currently in exclusive mode, any reset attempt will fail. We should receive the D3DERR_DEVICELOST state instead. This is what I got on my test machine and this is why it isn't crashing for me.

We don't handle this situation very well, In the vout code we have a FIXME for this:

/* FIXME what to do here in case of failure */
if (sys->reset_device) {                      
    if (ControlResetDevice(vd)) {             
        msg_Err(vd, "Failed to reset device");
        return VLC_EGENERIC;                  
    }

And we also have a FIXME in the core:

if (vout_display_Control(vd, VOUT_DISPLAY_RESET_PICTURES)) { 
    /* FIXME what to do here ? */                            
    msg_Err(vd, "Failed to reset pictures (probably fatal)");
}

One thing I'm not sure yet is whether the device can transition from the D3DERR_DEVICENOTRESET to the D3DERR_DEVICELOST before our restart attempt. This need some investigation.

One possible solution would be to do another restart attempt later if the first one failed (because the device will likely stay lost until the game exits exclusive mode).

See #8015 (closed) and #14135 (closed)

added Status::duplicate label

closed

mentioned in issue #11060 (closed)

mentioned in issue #14135 (closed)

crash when Battle Field 4 is running

Child items 0

Activity