Date: Mon, 24 Feb 2020 20:35:55 +0100 From: Michael Osipov <1983-01-06@gmx.net> To: Miroslav Lachman <000.fbsd@quip.cz> Cc: freebsd-ports@freebsd.org Subject: Re: Cannot build qt5-webkit with debug Message-ID: <15dbf933-b04b-788f-5cab-0dc5ffdcc532@gmx.net> In-Reply-To: <12ae3631-1973-5a42-8aa2-2fb8b9b93f8b@quip.cz> References: <f0a4e30f-8856-b4e6-dc9b-ad87ecf1a17a@quip.cz> <86c4b386-9298-fa0a-ccc1-ec6b1e65b788@quip.cz> <81e73790-6b69-8038-b087-9ff75c1cf9b5@gmx.net> <1a72bb7d-8ded-afe4-6fa7-8c301d73839e@quip.cz> <c5d41be9-f2a7-7451-b2e5-370587209571@gmx.net> <23335a73-5853-eab2-5684-b40f430ec8c7@quip.cz> <nycvar.OFS.7.76.44444.807.2002241744450.61731@z.fncre.vasb> <nycvar.OFS.7.76.44444.807.2002241750480.61731@z.fncre.vasb> <12ae3631-1973-5a42-8aa2-2fb8b9b93f8b@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 2020-02-24 um 19:10 schrieb Miroslav Lachman: > Marcin Cieslak wrote on 2020/02/24 18:51: >> On Mon, 24 Feb 2020, Marcin Cieslak wrote: >> >>> On Mon, 24 Feb 2020, Miroslav Lachman wrote: >>> >>> =C2=A0=C2=A0 frame #13: 0x00000008039aa3ed=20 >>> libQt5WebKit.so.5`WebCore::CSSParser::parseSheet(this=3D0x00007ffffff= fa490,=20 >>> sheet=3D0x00000008155f5e40, string=3D0x00007fffffffb888,=20 >>> textPosition=3D0x00007fffffffb650,=20 >>> ruleSourceDataResult=3D0x0000000000000000, logErrors=3Dfalse) at=20 >>> CSSParser.cpp:423:5 >>> >>> Looks like it has some trouble parsing font declarations in the=20 >>> HTML/CSS code you have been testing >>> on. This can be a webkit bug... >>> >>> Would be good to have a minimal HTML/CSS testcase to reproduce this=20 >>> and this should >>> probably be reported upstream. >> >> There is this report: >> >> https://github.com/qtwebkit/qtwebkit/issues/933 >> >> It says it crashes if you have no fonts installed (no TTF). >> >> Could this "fix" it? >=20 > Thank you for the tip, I will look at it. >=20 > > This is the code of the tested example - fetching from=20 > https://phantomjs.org/ >=20 > (root@testjail) ~/# cat /tmp/phantom.2.js > var page =3D require('webpage').create(); > page.onConsoleMessage =3D function(str) { > =C2=A0=C2=A0 console.log(str); > } > page.open('https://phantomjs.org/api/phantom/', function(status) { > =C2=A0=C2=A0 page.render('/tmp/beforeclick.png'); > =C2=A0=C2=A0 console.log(page.url); >=20 > =C2=A0=C2=A0 var element =3D page.evaluate(function() { > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 return document.querySelector('img[src = =3D=20 > "https://phantomjs.org/img/phantomjs-logo.png"]'); > =C2=A0=C2=A0 }); > =C2=A0=C2=A0 page.sendEvent('click', element.offsetLeft, element.offse= tTop, 'left'); >=20 > =C2=A0=C2=A0 window.setTimeout(function () { > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 console.log(page.url); > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 page.render('/tmp/afterclick.png'); > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 phantom.exit(); > =C2=A0=C2=A0 }, 5000); > =C2=A0=C2=A0 console.log('element is ' + element); > }); Looking at your sample code and the website, there are several issues: * The resource employs mixed site content HTTPS loads HTTP. Firefox=20 blocks this, I guess WebKit blocks it too. * Result: Droid Sans is not loaded [1], like the CSS * The CSS has this: > body { > font-family: 'Droid Sans','Lucida Grande',sans-serif; > line-height: 1.125em; > color: #444; } Lucida Grande isn't there either. It must choke somewhere. See also > frame #10: 0x00000008039cf92c libQt5WebKit.so.5`WebCore::CSSParser::par= seSystemFont I assume it does some fopen() and chokes on when looking for sans-serif=20 replacement. Can you run the application with truss? We should see the fopen() and=20 shortly after the crash. Upload the truss output. [1] http://fonts.googleapis.com/css?family=3DDroid+Sans:400,700 Michael
![https://phantomjs.org/img/phantomjs-logo.png"]')](https://phantomjs.org/img/phantomjs-logo.png){kind=link}
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15dbf933-b04b-788f-5cab-0dc5ffdcc532>