| 1 |
On 23/01/13 08:17, PaX Team wrote: |
| 2 |
> On 22 Jan 2013 at 19:44, Grant wrote: |
| 3 |
> |
| 4 |
>>>> google-chrome suffers intermittent crashes on x86 unless I enable |
| 5 |
>>>> softmode. Is there any other option to keep it running? |
| 6 |
>>> |
| 7 |
>>> can you get some details on the nature of crashes? any logs perhaps? |
| 8 |
>>> if softmode fixes it then it's probably MPROTECT related, did you |
| 9 |
>>> already disable it on the binary? |
| 10 |
>> |
| 11 |
>> MPROTECT is actually already disabled: |
| 12 |
> |
| 13 |
> ok, in that case can you report this |
| 14 |
> |
| 15 |
>> chrome[13338]: segfault at bbadbeef ip 14d81f2b sp 5ec2e1b0 error 6 in chrome[136f4000+4203000] |
| 16 |
> |
| 17 |
> to the chrome folks? i'm pretty sure that 'bbadbeef' is a magic constant |
| 18 |
> somewhere in their userland memory management code and signifies some |
| 19 |
> corruption (use-after-free perhaps?) and they'd probably like to know |
| 20 |
> how to reproduce this. |
| 21 |
> |
| 22 |
> |
| 23 |
webkit¿? |
Archives