General

Profile

benweint (Ben Weintraub)

Issues

Activity

08/15/2016

10:21 PM Ruby trunk Bug #12678 (Closed): No way to set a timeout for TLS handshake when using Net::SMTP
When establishing a connection to an SMTP server, Net::SMTP doesn't offer a way to specify a timeout for how long the...

08/02/2015

07:09 PM Ruby trunk Bug #11411 (Closed): Crash in rb_gc_mark() during Rails app boot with GC.stress=1
When booting a newly-initialized Rails 4.2.1 app under Ruby 2.2.2 with `GC.stress` enabled, I get a repeatable crash....

10/28/2014

07:03 PM Ruby trunk Bug #10443: Forking with contended mutex held can lead to deadlock in child process upon unlock
The original test case was not actually minimal (there's no need to attempt to re-acquire the lock in the forked chil...
03:42 PM Ruby trunk Bug #10443 (Open): Forking with contended mutex held can lead to deadlock in child process upon unlock
If a Ruby thread calls `Process.fork` while holding a Mutex (for example, within a `Mutex#synchronize` block) that is...

03/14/2014

08:44 PM Ruby trunk Bug #9629: GC::Profiler.total_time under-reports GC time compared to dtrace GC probe measurement
One minor follow-up: it's actually not that getrusage takes a 'long' time (relative to the cost of each lazy sweep in...

03/13/2014

10:53 PM Ruby trunk Bug #9629: GC::Profiler.total_time under-reports GC time compared to dtrace GC probe measurement
I think I've figured out the discrepancy here: the dtrace probes wrap around the getrusage(2) calls that GC::Profiler...
04:57 AM Ruby trunk Bug #9629: GC::Profiler.total_time under-reports GC time compared to dtrace GC probe measurement
I realized that these are actually measuring different things: dtrace's timestamps measure wall clock time, whereas G...
12:40 AM Ruby trunk Bug #9629: GC::Profiler.total_time under-reports GC time compared to dtrace GC probe measurement
Worth noting: a quick read through gc.c suggested that the missing GC sweep time might be due to me not having built ...
12:31 AM Ruby trunk Bug #9629: GC::Profiler.total_time under-reports GC time compared to dtrace GC probe measurement
Uploading the two files from that gist, just to keep everything in one place.
12:30 AM Ruby trunk Bug #9629 (Open): GC::Profiler.total_time under-reports GC time compared to dtrace GC probe measurement
I'm trying to square the numbers that I'm getting from GC::Profiler.total_time against those that I'm getting out of ...

Also available in: Atom