Software closes when a processing marker is deleted #67012

New Issue

Danilo · 2019-07-15T20:23:57+02:00

Danilo commented

2019-07-15 20:23:57 +02:00

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: GeForce GTX 750/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.13

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-11 13:50, hash: 06312c6d2d
Worked: (optional)

Short description of error
The software will close when you delete a marker while it has been tracked on motion tracking.

Exact steps for others to reproduce the error

Create a big marker on motion tracking to take some time to process.
Click on it and then click on "Track Markers"
Press "Delete" and click on "Delete Track"
Now Blender will close instantaneously.

**System Information** Operating system: Windows-10-10.0.17763 64 Bits Graphics card: GeForce GTX 750/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.13 **Blender Version** Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-11 13:50, hash: `06312c6d2d` Worked: (optional) **Short description of error** The software will close when you delete a marker while it has been tracked on motion tracking. **Exact steps for others to reproduce the error** - Create a big marker on motion tracking to take some time to process. - Click on it and then click on "Track Markers" - Press "Delete" and click on "Delete Track" - Now Blender will close instantaneously.

Danilo commented

2019-07-15 20:23:57 +02:00

Added subscriber: @danilolc

Sebastian Parborg commented

2019-07-17 11:05:32 +02:00

Added subscriber: @ZedDB

Sebastian Parborg commented

2019-07-17 11:05:32 +02:00

Does this still happen with the latest blender beta and nvidia drivers?

Brecht Van Lommel commented

2019-07-17 11:37:29 +02:00

Added subscribers: @Sergey, @brecht

Brecht Van Lommel commented

2019-07-17 11:37:29 +02:00

I doubt this is related to graphics drivers, probably it's deleting data that the tracking is using in another thread.

Sebastian Parborg commented

2019-07-17 11:43:39 +02:00

I know, I'm just eliminating any other factor in the small chance that they were the issue.

Philipp Oeser commented

2019-07-17 11:52:17 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2019-07-17 11:52:17 +02:00

Can confirm here, checking...

Philipp Oeser commented

2019-07-17 12:00:53 +02:00

crash on framenr < track->markers- [x].framenr, where track->markers is garbled... will check with ASAN...

1  BKE_tracking_marker_get                                    tracking.c           1339 0x1fd0999      
2  BKE_tracking_marker_get_exact                              tracking.c           1380 0x1fd0b33      
3  accessor_get_mask_for_track_callback                       tracking_util.c      940  0x1fdb012      
4  (anonymous namespace)::LibmvFrameAccessor::GetMaskForTrack frame_accessor.cc    120  0x31c8e3a      
5  mv::(anonymous namespace)::GetMaskForMarker                autotrack.cc         118  0x31d1775      
6  mv::AutoTrack::TrackMarker                                 autotrack.cc         164  0x31d19bc      
7  libmv_autoTrackMarker                                      autotrack.cc         63   0x31c5012      
8  autotrack_context_step_cb                                  tracking_auto.c      424  0x30944ab      
9  parallel_range_single_thread                               task.c               1103 0x20fc958      
10 BLI_task_parallel_range                                    task.c               1147 0x20fcb33      
11 BKE_autotrack_context_step                                 tracking_auto.c      452  0x30945ec      
12 track_markers_startjob                                     tracking_ops_track.c 233  0x2da19e6      
13 do_job_thread                                              wm_jobs.c            383  0x23e16b2      
14 tslot_thread_start                                         threads.c            260  0x20fd5f0      
15 start_thread                                                                         0x7ffff488b5a2 
16 clone                                                                                0x7ffff1c1f303

crash on `framenr < track->markers- [x].framenr`, where `track->markers` is garbled... will check with ASAN... ``` 1 BKE_tracking_marker_get tracking.c 1339 0x1fd0999 2 BKE_tracking_marker_get_exact tracking.c 1380 0x1fd0b33 3 accessor_get_mask_for_track_callback tracking_util.c 940 0x1fdb012 4 (anonymous namespace)::LibmvFrameAccessor::GetMaskForTrack frame_accessor.cc 120 0x31c8e3a 5 mv::(anonymous namespace)::GetMaskForMarker autotrack.cc 118 0x31d1775 6 mv::AutoTrack::TrackMarker autotrack.cc 164 0x31d19bc 7 libmv_autoTrackMarker autotrack.cc 63 0x31c5012 8 autotrack_context_step_cb tracking_auto.c 424 0x30944ab 9 parallel_range_single_thread task.c 1103 0x20fc958 10 BLI_task_parallel_range task.c 1147 0x20fcb33 11 BKE_autotrack_context_step tracking_auto.c 452 0x30945ec 12 track_markers_startjob tracking_ops_track.c 233 0x2da19e6 13 do_job_thread wm_jobs.c 383 0x23e16b2 14 tslot_thread_start threads.c 260 0x20fd5f0 15 start_thread 0x7ffff488b5a2 16 clone 0x7ffff1c1f303 ```

Sergey Sharybin self-assigned this 2019-07-17 12:28:05 +02:00

Sergey Sharybin commented

2019-07-17 12:28:05 +02:00

This is a missing check for the track in the movie clip being still available when synchronizing tracking data from Libmv to Blender.

blender-admin commented

2019-09-13 11:48:22 +02:00

This issue was referenced by 592a3d7b47

This issue was referenced by 592a3d7b4771c8d329d586e8bfa776b25666921b

Sergey Sharybin commented

2019-09-13 12:08:41 +02:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2019-09-13 12:08:41 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Software closes when a processing marker is deleted #67012