Anthony J. Bentley wrote:
> Yes, if I remove websearch I can reproduce this in 3.7 on amd64.
> Thanks for finding a reliable trigger; I've reported it upstream.
Thanks for reporting it! I reckon I should finally subscribe to their lists.
To add to what you had submitted here[1]: in case when it
Cág writes:
> Anthony J. Bentley wrote:
>
> > So far I haven't been able to reproduce this crash.
>
> I think I've found the reason. If I remove [websearch] from the toolbar
> (Customise menu entry), it dumps the core with that error. If I don't,
> it's fine. Could you try it with 3.6 and 3.7?
Yes
Anthony J. Bentley wrote:
> So far I haven't been able to reproduce this crash.
I think I've found the reason. If I remove [websearch] from the toolbar
(Customise menu entry), it dumps the core with that error. If I don't,
it's fine. Could you try it with 3.6 and 3.7?
> Can you try with the 3.7
Cág writes:
> > > Now, netsurf-gtk. It crashes rarely, 1 in 7, maybe 1 in 10:
> > Looks like a use-after-free of type_instance.
>
> It also happens when double clicking on a link in History (Ctrl+Shift+H).
So far I haven't been able to reproduce this crash. Can you try with the
3.7 update I just s
Stuart Henderson wrote:
>> It also happens when double clicking on a link in History (Ctrl+Shift+H).
> Sounds like a bug :-)
Is it a Netsurf's bug? Or glib's, which file it mentions?
--
caóc
On 2017/10/21 17:20, Cág wrote:
> Stuart Henderson wrote:
>
> > This is likely to have been fixed with a post-6.2 commit to the chromium
> > port. I *think* you can probably still just get away with running the
> > snapshot package on 6.2.
>
> I think it's fine. They only differ by a revision. It
Stuart Henderson wrote:
> This is likely to have been fixed with a post-6.2 commit to the chromium
> port. I *think* you can probably still just get away with running the
> snapshot package on 6.2.
I think it's fine. They only differ by a revision. It doesn't crash now,
well, yet, at least.
> >
On 2017/10/21 16:08, Cág wrote:
> Hi,
>
> Previously, when Chromium was gtk+2 based, it could be started within 1-3
> attempts. Now it takes from five to ten. The message is still the same:
This is likely to have been fixed with a post-6.2 commit to the chromium
port. I *think* you can probably s
Hi,
Previously, when Chromium was gtk+2 based, it could be started within 1-3
attempts. Now it takes from five to ten. The message is still the same:
chrome($PID) in free(): use after free 0x$HEX
and
---
Program received signal SIGABRT, Aborted.
thrkill () at -:3
3 -: No such file or dire
