hard Crach during Soliving a motion Track #44120
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#44120
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Ubuntu 14.04
NVIDIA GeForce GT 555M
Blender Version
Broken: 2.73.0a
bbf09d9
, RC2 2.74.01f547c1
Short description of error
Craches during solve
Exact steps for others to reproduce the error
Open attached file and solve
track5Fail.blend
Changed status to: 'Open'
Added subscriber: @Leon95
Console Output:
Windows 7 64Bit, with 2.74 RC2
Crashes also, Console Output:
track5Fail.crash.txt
Added subscriber: @Sergey
Track.003 has some weird frame number of few millions, which does not seem to be correct and most likely caused by error in some tool. So in order to fix the crash we need to figure out which tool produced such a bad track.
And for that we need your input about how to reproduce such a corrupted file form non-corrupted state.
my last backup file is track3.blend, wich solves without problems
I worked with my build of (unmodified) master of 28.1.2015 i think
with this file i used the original video file: 00019.MTS(on pasteall because of file-size limit, delete extention ".blend")
wich causes some trouble, because of the compression. so, in the last session (now with RC2) I converted the video to a png sequence, and i decided to track the whole video (not only until frame 126). Then I can't solve the motion, I have no idea why.
"Track.003" seems to have no keyframes (displayed) in the timeline and shoud be disabled the whole time... then it schoud not have an impact in the solve. I dont want to use the track anyway, because it was bad tracked.
Have I have to upload the png seqence to? (about 230MB would take ages, only exported with default settings)
What do you mean with weird frame number?
Track.003 does have two markers: first one is at frame 0 which is muted, second one is at frame 109147000 which is keyframed and non-muted. Such frame number should not happened i guess.
For reproducing the issue it's not enough to have files, it's also crucial to know exact steps which makes the track corrupted.
Then i have no idea... I know only that Blender crashed a few times during prfetching the video file, when the current frame ist not 0 or 1. (which is caused by a not activated swap, i think) I used the autosaved files a few times. it is maybe saving error, but I don't think that it is reproducable.
Maybe it can be fixed if the code ignores keyframes higher then 300000, wich the timeline can't display, but thats not ideal. I do some testing but i don't think that i can reproduce.
By the way, a backward prfetching with a compressed video file (wich appears when the current frame is in the middle of the video and the prefetch reaches the end) is not ideal, high cpu and compression issues. (better prefetch only forward)
Changed status from 'Open' to: 'Archived'
not reproducable, will reopen if I find something.
whops, sry i dont want to assign this to you, @testscreenings. this is a bug in the phabricator website by using the batch editor...