ruby.git/process.c, branch v4.0.3 The Ruby Programming Language Reorganize page documentations (#15154) 2025-11-27T20:12:24+00:00 Stan Lo stan001212@gmail.com 2025-11-27T20:12:24+00:00 4cd6661e1853930c8002174c4ccd14f927fcd33b Re-organize page docs 
Re-organize page docs
 Adjust indent [ci skip] 2025-11-24T08:30:47+00:00 Nobuyoshi Nakada nobu@ruby-lang.org 2025-11-24T08:30:47+00:00 45fcb9d590d36c469e7fa18790fafd51809943ee 






Replace vfork with fork for ASAN
2025-11-23T18:54:44+00:00

Peter Zhu
peter@peterzhu.ca

2025-11-23T17:47:33+00:00

390220579b7afe433731f4d2d119a57858e27911

Older versions of ASAN do not support vfork. See https://github.com/google/sanitizers/issues/925





Older versions of ASAN do not support vfork. See https://github.com/google/sanitizers/issues/925







Run rb_gc_before_fork after before_exec
2025-11-20T22:30:42+00:00

Peter Zhu
peter@peterzhu.ca

2025-11-18T22:07:21+00:00

2447380894e8ab4968d745f6844d2dc5278ebd6b

before_exec stops the timer thread, which requires locking the Ractor
scheduler lock. This may deadlock if rb_gc_before_fork locks the VM.





before_exec stops the timer thread, which requires locking the Ractor
scheduler lock. This may deadlock if rb_gc_before_fork locks the VM.







[DOC] Fix formatting of seconds parameter in documentation
2025-09-24T10:06:24+00:00

Ricardo Trindade
ricardo.trindade743@gmail.com

2025-09-24T10:06:24+00:00

48eb907f6bbf17e7a5ad1a4e68b7843cd2a3ccb7

There's an additional colon sign in the documentation for Process.clock_gettime





There's an additional colon sign in the documentation for Process.clock_gettime







Combine rb_imemo_tmpbuf_auto_free_pointer and rb_imemo_tmpbuf_new
2025-09-15T13:25:20+00:00

Peter Zhu
peter@peterzhu.ca

2025-09-13T18:10:57+00:00

b0ce1fd549a3227ef4d9f65e4cdf0df93e4adeb0












Disallow forking from non-main ractor
2025-06-24T14:10:40+00:00

Jean Boussier
jean.boussier@gmail.com

2025-06-24T10:33:27+00:00

5bcc639b341291fe0584d11c6bdd1add29f40087

[Bug #17516]

`fork(2)` only leave the calling thread alive in the child.
Because of this forking from the non-main ractor can easily
leave the VM in a corrupted state.

It may be possible in the future to carefully allow forking from non-main
Ractor, but shot term it's preferable to add this restriction.





[Bug #17516]

`fork(2)` only leave the calling thread alive in the child.
Because of this forking from the non-main ractor can easily
leave the VM in a corrupted state.

It may be possible in the future to carefully allow forking from non-main
Ractor, but shot term it's preferable to add this restriction.







Suppress warnings by gcc-13 with `-Og`
2025-06-05T13:33:02+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2025-06-05T13:22:24+00:00

edaa27ce45dacd5e972781105a8e7ba4abe77c3d












Use RB_VM_LOCKING
2025-05-25T06:22:43+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2025-05-23T11:14:20+00:00

aad9fa285398d48b5647f8a36922b8d817a24156












Acquire VM lock around fork
2025-05-08T17:53:28+00:00

John Hawthorn
john@hawthorn.email

2025-05-07T02:08:02+00:00

d7ad53f249de459190d88bcb16c819411226be46

Otherwise it might be held by another Ractor, causing a deadlock in the
new process.





Otherwise it might be held by another Ractor, causing a deadlock in the
new process.