トップ > 交流 >雑談 >最新版の修正情報で気になったもの

Re: 最新版の修正情報で気になったもの

169件表示 すべてのコメント一覧へ

投稿ツリー


このトピックの投稿一覧へ

通常 Re: 最新版の修正情報で気になったもの

msg# 1.47
depth:
1
前の投稿 - 次の投稿 | 親投稿 - 子投稿なし | 投稿日時 2014/1/24 10:46
完全無欠猫  長老 居住地: 兵庫  投稿数: 750
今回は長文の解説文が多いです。
Crash関係:
SHA-1: 0f72a8a7f0a0f8fff11ee26859c33ab684d6e19b
* Fix T38337: Crash when calling to_mesh() on a Curve object after clearing its parent
　This is rather a workaround which only works because curve evaluation is only called
　for a temporary object. Not a big deal if we'll skip path creation for such objects.
　Still would need to think of general solution.

SHA-1: 26ae14d2dccd0d34edfe9f26a4126e9a69e74983
* Fix crash when changing space type to 3D space when having multiple windows
　it is possible that different windows shares scene but displays different
　layers. And it's also possible that different areas in the same window will
　show different layers.
　First case was violated in `dag_current_scene_layers()` which only checked
　scene layers only once and if multiple windows shares the same scene only
　one window was handled. Now made it so layers from all windows will be
　squashed together into a single `DagSceneLayer`. This mainly solves issue
　with `DAG_on_visible_update()` which didn't work reliable with multiple
　open windows.
　Second case required call of `DAG_on_visible_update()` when changing space
　are type.
　This commit slows things a bit actually because `dag_current_scene_layers()`
　is actually called on every main WM loop iteration. It is possible to speed
　some logic up perhaps. Not sure it's so much critical to do now because there
　are unlikely to be more than few windows open anyway.
　Will rather think of skipping all that flushing things if no objects are
　tagged for update actually.

SHA-1: 64bd4be6b2d9d093c56e6cce809d8cd1650ebe6f
* Fix for crash getting the name of RNA properties with empty name

SHA-1: cbdedc169dd948d308dcdb1fc2e74b1fdd25880c
* Fix T38284: Crash with several shrinkwrap constraint using same target
　Issue is caused by the race condition between getting custom data layers
　from target's derived mesh (for vertices and faces) and releasing this
　derived mesh from other threads.
　When one releases the derived mesh it'll free temporary data from it,
　and it'll also update data layers mapping.
　General rule for threading is that no one is ever allowed to modify
　data he doesn't own. This means that no temp layers are to be allocated
　in derived mesh and making it so `CustomData_free_temporary()` doesn't
　update mapping if nothing was freed will solve the race condition.
　It is still possible to do other improvements, namely detect which
　additional data/layers are to be present in derived mesh and create
　it as a part of `object_handle_update()`, but this is to be solved
　separately.

少し意味合いが異なりますがCrash関係ということで・・・
SHA-1: 4b820fb673319989026433f284e11671885757c0
* Fix T38311: cycles BVH cache crash on Windows.

投票数:0 平均点:0.00

  条件検索へ

ログイン

ユーザ名:

パスワード:



パスワード紛失

クイックリンク

2021/07/01版
●Blender.org
BlenderFoundation
- Blenderのダウンロード
- 公式チュート等
- 公式マニュアル（和訳）

●ニュース(英文)
BlenderNation

●Blenderコミュニティ
blenderartists.org

●Blender Q&A
- Blender Stack Exchange

●テストビルド
Buildbot(自動生成)


●開発関連
公式開発サイト
Blender開発blog
Blender Wiki