# V8 isolate因时间跳跃而崩溃

**URL:** <https://meta.discourse.org/t/crash-due-to-v8-isolate-forked-when-time-skips-forward/213194>\
**Category:** Bug\
**Created:** [2021 年12 月 27 日 15:59 UTC](https://meta.discourse.org/t/crash-due-to-v8-isolate-forked-when-time-skips-forward/213194 "2021-12-27T15:59:58Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

作者： ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
发布日期： [2022 年1 月 4 日 10:46 UTC](https://meta.discourse.org/t/crash-due-to-v8-isolate-forked-when-time-skips-forward/213194/5 "2022-01-04T10:46:41Z")

</div>

此问题已在

> <https://github.com/discourse/message_bus/commit/60eda3d783e4cb71e3f0a5ed6de949319503be3e>
>
> Previously if message bus stalled for 3 \* keepalive (default 60 seconds)
> it woul…d terminate itself.
> 
> This causes pathological issues when a bus is in readonly mode and is a
> very unsafe default.
> 
> The reasoning for the keepalive check was to ensure the bus it always
> functioning, the remediation was deescalated to a log warning.

中修复，并已合并到 Discourse 中：

> <https://github.com/discourse/discourse/commit/80e751543d51246d791e7c53a32d478e4fd072f8>
>
> Bumps \[message\_bus\](https://github.com/discourse/message\_bus) from 3.3.8 to 3.4.…0.
> \- \[Release notes\](https://github.com/discourse/message\_bus/releases)
> \- \[Changelog\](https://github.com/discourse/message\_bus/blob/main/CHANGELOG)
> \- \[Commits\](https://github.com/discourse/message\_bus/compare/v3.3.8...v3.4.0)
> 
> \---
> updated-dependencies:
> \- dependency-name: message\_bus
> dependency-type: direct:production
> update-type: version-update:semver-minor
> ...
> 
> Signed-off-by: dependabot\[bot\] \<support@github.com\>
> 
> Co-authored-by: dependabot\[bot\] \<49699333+dependabot\[bot\]@users.noreply.github.com\>

感谢 @bennofs 的详细报告！

---

_[View the full topic](https://meta.discourse.org/t/crash-due-to-v8-isolate-forked-when-time-skips-forward/213194)._