|
31 | 31 | </header> |
32 | 32 | <p>This document describes the changes made to the ERTS application.</p> |
33 | 33 |
|
| 34 | +<section><title>Erts 13.2.2</title> |
| 35 | + |
| 36 | + <section><title>Fixed Bugs and Malfunctions</title> |
| 37 | + <list> |
| 38 | + <item> |
| 39 | + <p> |
| 40 | + If a runtime system which was starting the distribution |
| 41 | + already had existing pids, ports, or references referring |
| 42 | + to a node with the same nodename/creation pair that the |
| 43 | + runtime system was about to use, these already existing |
| 44 | + pids, ports, or references would not work as expected in |
| 45 | + various situations after the node had gone alive. This |
| 46 | + could only occur if the runtime system was communicated |
| 47 | + such pids, ports, or references prior to the distribution |
| 48 | + was started. That is, it was extremely unlikely to happen |
| 49 | + unless the distribution was started dynamically and was |
| 50 | + even then very unlikely to happen. The runtime system now |
| 51 | + checks for already existing pids, ports, and references |
| 52 | + with the same nodename/creation pair that it is about to |
| 53 | + use. If such are found another creation will be chosen in |
| 54 | + order to avoid these issues.</p> |
| 55 | + <p> |
| 56 | + Own Id: OTP-18570 Aux Id: PR-7190 </p> |
| 57 | + </item> |
| 58 | + </list> |
| 59 | + </section> |
| 60 | + |
| 61 | +</section> |
| 62 | + |
34 | 63 | <section><title>Erts 13.2.1</title> |
35 | 64 |
|
36 | 65 | <section><title>Fixed Bugs and Malfunctions</title> |
|
0 commit comments