Originally Posted by rinigus

@Zeta: On normal systems you would usually see OOM killer in dmesg. Not sure it is there in SFOS. I have not thought that this app would take too much RAM. On my phone it takes about 100 MB RSS (250 MB virtual). Shouldn't be too much, I guess.

However, looks like there is something fishy with memory handling going on. I presume that OOM would not result in SIGSEGV in free(). Maybe someone can help us with tutorial on how to get debug symbols into your backtraces...

Originally Posted by rinigus

Maybe someone can help us with tutorial on how to get debug symbols into your backtraces...

Originally Posted by rinigus

I have managed to compile Mapbox GL Native for SFOS and tested it with the small app. All seems to be working as expected. Even in online mode, its fast, allows smooth transitions and so on.

Originally Posted by rinigus

SFOS packaging: Compilation relies on recent gcc (using 6.4.0, https://build.merproject.org/package...oolbox/opt-gcc). The compiled Qt version of the library is available at https://build.merproject.org/package...maps/qmapboxgl on the basis of https://github.com/rinigus/pkg-mapbox-gl-native .

QML integration: At present, Mapbox GL Native development is targeting Qt/QML through QtLocation 5.9 plugin. As a result, direct interface with QML was removed in the beginning of March 2017.

I have made a small project that would allow us to interface Mapbox GL through QML at https://github.com/rinigus/mapbox-gl-qml . Idea is to compose the interface that can be used by mapping applications for showing and interacting with the maps. Interface between OpenGL and QML is based on the same approach as used in the current implementation for QtLocation. This looks to be compatible with Silica as well, as much as I tested.

Originally Posted by rinigus

Small SFOS app is available at https://github.com/rinigus/mapbox-demo-sfos and shows how to integrate developed QML interface into the app as well as the integration with gcc-6.4.0.

I am letting you know about the development early, so we can discuss the ways we can integrate it with the available map applications (Poor Maps, modRana, Maep, and others). There is plenty to do, but all seems to be doable at this stage and shouldn't take a while before we'll get the map applications based on OpenGL rendering. Ideally, we should keep the same source code trees for tile-based and OpenGL map applications.

Originally Posted by Zeta

I got lost when trying it before, as gdb was giving commands to install them with "zypper", which appears to not be the good package manager on the Jolla (I am not far of 1 package manager per device I use, so it is sometime difficult to remember which one is used where....)

Code:

pkcon install glibc-debuginfo

Seems to do the trick.

The latest full trace and memory mapping with this are here : https://pastebin.com/Dmr34wGS
and https://pastebin.com/gs9Jv0VT


It never fail at the same place for me, but in my last tests this appends mostly around malloc/free calls.

By the way, I may have not said it before, there is a warning that I didn't take seriously before as it mostly works, but anyway, here it is:

Code:

[nemo@Sailfish ~]$ mapbox-sfos 
[D] unknown:0 - Using Wayland-EGL
[W] unknown:0 - Could not find any zN.M subdirs!
[W] unknown:0 - Theme dir "/usr/share/themes/jolla-ambient/meegotouch/z1.0/" does not exist

Originally Posted by MartinK

...

Yeah, that sounds to me as the way to go. We still can't use any form of Qt Location for Jolla Store apps, so depending on Qt Location from Qt 5.9 when another Qt 5 update on Sailfish OS is not even on the horizon is really a no-go.

Originally Posted by MartinK

What is the QML interface of the element like going to look like & what features will it likely support ?
Eq.: Just map centering, zooming control, etc. or more advanced stuff like POI markers any polyline display (routing trace/track logs) ? I've took a quick a for documentation of the upstream mapbox/mapbox-gl-native API and have not been really able to find a clear answer.

Originally Posted by MartinK

I'll likely integrating this map view first as an alternative option to the current fully tile based map view. At least until the features people expect to work (polylines, markers, maybe also overlays ?) can be provided by the Open GL based view as well.

Originally Posted by MartinK

BTW, what about offline usage ? Looking at the available documentation the widget seems to be basically locked to Mapbox for the input data for it's map rendering. How feasible does it look like making it (optionally ?) consume locally available data packs managed by OSM Scout Server and hosted @ modrana.org (as we already do with the other data packs) ?

Originally Posted by elros34

Testing: mapbox-sfos 0.1+master.20170916171905.daedaf3-10.6.1.jolla

Device: Photon Q
SFOS version: 2.1.0.11
Helsinki, Punavuori, Kluuvi looks correct but Fabianinkatu and few others flick when Bearing or pitching.
There are also other artefacts: black rectangle in top left corner and black flicking lines when bearing or pitching.
gdb log: https://pastebin.com/HyeSExgU

Code:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x4637c390 (LWP 8020)]
0x43502948 in ?? ()
(gdb) bt full
#0  0x43502948 in ?? ()
No symbol table info available.
#1  0x4350f988 in ?? ()
No symbol table info available.
#2  0x4350f988 in ?? ()
No symbol table info available.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

/proc/pid/maps gives me:
434be000-43593000 r-xp 00000000 103:05 79376 /system/lib/egl/libGLESv2_adreno200.so
I guess it's not good.