**** BEGIN LOGGING AT Thu Sep 24 02:59:58 2015 Sep 24 05:54:00 moin Sep 24 06:29:53 morning Sep 24 07:08:03 morning Sep 24 07:15:30 Tofe: ping Sep 24 07:23:42 Morning Sep 24 07:23:46 Herrie: pong Sep 24 07:29:33 Tofe: You had a chance to test nanobrowser on device yet? Sep 24 07:34:56 No, not yet; I've just started a new build at home with jansa/fido branch, to have a look Sep 24 07:35:26 OK :) Sep 24 07:36:23 I'll play a bit with some of the browser things like certificate dialog and permission requests so we can put those in luneos-components. There's standard implementation but need to style it a bit :) Sep 24 07:39:39 Herrie|Veer: note that starting nanobrowser should be quite easy, if you want to know if it works Sep 24 07:47:27 I don't think I have it on my device currently Sep 24 07:51:16 oh? ok Sep 24 07:51:44 I flashed latest nightly which doesn't have webengine :P Sep 24 07:52:30 ah yes, in that case, I understand :) Sep 24 07:52:33 morphis: Based on your comment last night with qtwebkit for Enyo 1 and qtwebengine for Enyo 2 and others it might make sense to include both in builds for now? Sep 24 07:59:31 Herrie|Veer: if the size still fits on our devices, then yes Sep 24 08:06:42 morphis: Seems build size is 23MB difference. Not sure if the 23MB larger once has webkit too, but I guess it has since browser and apps run fine. Sep 24 08:07:19 Herrie|Veer: I am more worried if that is bigger than for example the partition we allocate on the tp Sep 24 08:08:51 Seems 25MB extra on TP Sep 24 08:09:00 303 vs 327, Sep 24 08:09:27 But that's compressed of course Sep 24 08:09:36 Need to check unpacked Sep 24 08:10:02 please do that Sep 24 08:27:58 I'll double check how much free space I have tonight on TP. Sep 24 08:28:44 I installed an image with both without issues, but don't recall if I created a 1 or 2GB partition. I suspect a 2GB one. Sep 24 08:30:45 The binaries aren't that big -- it's the debug infos that are a resource hog Sep 24 16:36:21 ka6sox: ping Sep 24 16:36:31 Tofe: ping Sep 24 17:07:08 Herrie: pong Sep 24 17:07:27 Herrie: I'm currently flashing the jansa/master build of today :) Sep 24 17:22:00 Herrie: same thing with nanobrowser on latest QtWebEngine (QtWebEngineProc crashes) Sep 24 17:43:14 Tofe: Good to know it's not our browser at least :P Sep 24 17:43:49 For the webengine in build, do we have all these debug infos in there? Sep 24 17:45:25 Herrie|Veer: yes, I just fear the device will explode if I debug webengne :D Sep 24 17:46:45 the dbg *package* is 600MB... Sep 24 18:20:18 Tofe: Yeah I guess the TP with 1GB memory won't like it :P Sep 24 18:24:43 And I don't know how to debug a QtWebEngineProcess... Simply to get a stack of something... Sep 24 18:31:19 Did you try 5.5.1 already? Sep 24 18:31:28 To see if that sorts stuff? Sep 24 18:31:45 I don't see any errors in my journalctl for the webengine crashing Sep 24 18:38:29 No, JaMa's branch is still built upon 5.5.0 Sep 24 18:38:59 only the web engine has been updated to the latest commits of 5.5 Sep 24 18:39:39 Ah ok Sep 24 19:08:40 Ok I'm able to catch the segfault within QtWebEngineProcess, but it doesn't really help: the segfault occurs within libQt5WebEngineCore.so.5.5.0, and the corresponding debug file is... 1.4Gb. Sep 24 19:29:29 Tofe: ouch Sep 24 19:31:00 yup... But I've got an idea: I'll try cross-architecture gdb debugging :p Sep 24 20:12:42 After some struggles, here it come! http://pastebin.com/y3ZGNUUk Sep 24 20:14:16 oh wait, no, it's not that one :p This is only one of the many threads Sep 24 20:25:42 This is our crash: http://pastebin.com/FtyJK5i5 Sep 24 20:27:23 This could be related to a problem with fonts... but I don't know much more... Sep 24 20:58:29 Tofe: I've sent it to ML, but haven't merged it to jansa/master yet in meta-qt5, still testing it and fixing the issues **** ENDING LOGGING AT Fri Sep 25 02:59:58 2015