Ichthyostega
100252acdf
...whenever the planning falls behind schedule, it can happen that the planner-worker immediately dispatches its own jobs; while the calculation is broken anyway in this situation, especially this call scheme leads to dropping the Grooming-Token prior to the calculation dispatched directly. Since the dependency relation can only be established after creating both predecessor and successor schedules, the corresponding allocation of the NOTIFY-Activity is not protected against concurrent access, which probably leads to the assertion failure due to corruption of the allocator's internal data structures... |
||
|---|---|---|
| .. | ||
| draw | ||
| DIR_INFO | ||
| empty.html | ||
| InterfaceConcept_Varga.mm | ||
| renderengine.html | ||
| thinkPad.ichthyo.mm | ||
| uml | ||
| workflow.mm | ||