[lkml]   [2016]   [Jul]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [4.7+] various memory corruption reports.
On Fri, Jul 29, 2016 at 11:05:14AM -0400, Dave Jones wrote:
> I've just gotten back into running trinity on daily pulls of master, and it seems pretty horrific
> right now. I can reproduce some kind of memory corruption within a couple minutes runtime.
> ,,,
> I'll work on narrowing down the exact syscalls needed to trigger this.

Even limiting it to do just a simple syscall like execve (which fails most the time in trinity)
triggers it, suggesting it's not syscall related, but the fact that trinity is forking/killing
tons of processes at high rate is stressing something more fundamental.

Given how easy this reproduces, I'll see if bisecting gives up something useful.


 \ /
  Last update: 2016-07-29 18:01    [W:0.059 / U:2.112 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site