Page MenuHome

Motion Tracking Crash
Closed, ArchivedPublic

Description

System Information
Operating system:Windows11
Graphics card:RTX3050Ti 4G
RAM:16G

Blender Version
Broken: 3.0.1
Worked: 3.0.1

Short description of error
My video have 3300 frames.
At Page "Motion Tracking",when I click CTRL+T then Blender crashes at 12%.
Then I open Windows Task Manager,16G RAM used 15.4G

ps: If it isn’t a bug (or just bescause I don‘t have enough RAM),so hope to rebuild motion tracking code to improve memory utilization.

PS
I‘m sorry about my description.I just a Chinese Student,so my English is petty bad

Event Timeline

Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Needs Information from User.Jan 31 2022, 3:53 PM

Thanks for the report, but for the development team to be able to help, there needs to be reproducible steps (start blender, press this, then that and crash).

So please attach a simplified .blend file saved right before the bug occurs, so only a few steps are needed to trigger the bug.

(Normally .blend files can be simplified by removing most objects and disabling settings, until the problem reveals itself more clearly).

Thanks for the report, but for the development team to be able to help, there needs to be reproducible steps (start blender, press this, then that and crash).

So please attach a simplified .blend file saved right before the bug occurs, so only a few steps are needed to trigger the bug.

(Normally .blend files can be simplified by removing most objects and disabling settings, until the problem reveals itself more clearly).

You have not attached either .blend file or video. It was a mistake?

I am so sorry about that,sir.

Thanks for the file, but I still can't replicate the problem because the "anim file doesn't exist: ...\源_1.mp4"
Videos are not packed together with blender, they need to be attached separately.
Without being able to replicate the problem there's not much we can do here yet :\

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks for the report. If the problem persists please open a new report with the required information.