Crash while panning the map #489
Comments
|
Hi @mathgil Do you have the possibility to connect your device with a cable to a computer and run |
|
Hi, thanks for the answer !
I think I managed to do something.
I activated usb debug mode on the device. It allows me to see it on Android
Studio. I set on "Verbose" and filtered it with "QField".
Here's the log. Hope it helps.
*VERBOSE*
https://gist.github.com/m-kuhn/a692a3c5015f9002e4a5dda7ec89f048
Some more info :
I do not use Qfield import/export plugin in Qgis since I already use
geopackage files.
I noticed that it all worked when I copy/paste my project (saved in .qgs -
since qgz does not appear to be supported ?) with all the files in the
native file tree on my mobile device. It allows me to cut the export step.
I just overwrite my geopackage files from my mobile device to my desktop
computer back to office.
Nethertheless, I have to save again the .qgs file into Qgis 2,18, then
reopen it in Qgis 3,X, to make it openable in Qfield. If no, Qfield cannot
manage to open the project. Why... ? File size change during the process,
so I think Qgis 3,x lose something when converting .qgz to .qgs
Looking at the log, it seems that there is a version conflict. But on my
old device, I've never encountered bug like this. Maybe some light
instability sometimes.
Le mar. 26 févr. 2019 à 09:32, Matthias Kuhn <notifications@github.com> a
écrit :
… Hi @mathgil <https://github.com/mathgil>
Do you have the possibility to connect your device with a cable to a
computer and run logcat (you will need to install android studio) and
attach the output during a crash here?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#489 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AttykXwTPrwGvocNBrAgfMQniOrTPmiPks5vRPEFgaJpZM4bOYIU>
.
--
|
|
That's very good. Regarding the version, QGIS 2.18 is end of life. While we don't actively prevent using projects produced with QGIS 2.18 we also won't invest on that unless a customer project requires it. Supporting .qgz project is on the todo list, but it shouldn't change anything. To control, you can unzip the qgz file and compare the .qgs file contained inside. |
|
This one is complete, sorry.
https://gist.github.com/m-kuhn/f0c023f3052ee882cdc5b4c865ed08ca
|
|
Hmmm, I see QField loading and starting up, but I can't find the information related to the crash in there. |
|
Yes, it did.
I can see this line at 14:15:12.806.
2019-02-26 14:15:12.806 9158-9209/? W/QField: QFontEngineFT: Failed to
create FreeType font engine
--------- beginning of crash
2019-02-26 14:15:12.949 9158-9209/? A/libc: Fatal signal 11 (SIGSEGV),
code 1, fault addr 0x0 in tid 9209 (QtThread)
etc...
Is that you looking for ?
Pay attention : I sent you 2 messages, the first was incomplete, the second
was complete (sent at 14:23).
Le mar. 26 févr. 2019 à 14:33, Matthias Kuhn <notifications@github.com> a
écrit :
… Hmmm, I see QField loading and starting up, but I can't find the
information related to the crash in there.
Did it crash while you were recording?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#489 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Attykddmm1Z3Z-DV1JnXXR2iaSR8IFMOks5vRTeygaJpZM4bOYIU>
.
--
|
|
Hmm... I can't find Maybe it's too long for github comments to manage. Can you paste it on https://gist.github.com and paste a link here? |
|
Link :
https://gist.github.com/mathgil/69dcced23b9ed6219b3494c558759cda
Thanks to the time you allow to my problem. :)
Le mar. 26 févr. 2019 à 15:32, Matthias Kuhn <notifications@github.com> a
écrit :
… Hmm... I can't find beginning of crash in your message
Maybe it's too long for github comments to manage. Can you paste it on
https://gist.github.com and paste a link here?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#489 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AttykW1IIcxiPfgYxIca2KUlCBU4rhIFks5vRUWJgaJpZM4bOYIU>
.
--
|
|
Thanks, the interesting part is here: but unfortunately it's not immediately visible what's the problem. Can you try the latest builds (download apk here) |
|
Here's the log with the apk you just linked to me.
It crashed again.
https://gist.github.com/mathgil/1e8e0926c55e16298c65b3d33c63dfcb
Le mar. 26 févr. 2019 à 16:02, Matthias Kuhn <notifications@github.com> a
écrit :
… Thanks, the interesting part is here:
2019-02-26 14:15:13.074 9224-9224/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2019-02-26 14:15:13.074 9224-9224/? A/DEBUG: Build fingerprint: 'samsung/jackpotltexx/jackpotlte:8.0.0/R16NW/A530FXXU3BRK3:user/release-keys'
2019-02-26 14:15:13.074 9224-9224/? A/DEBUG: Revision: '7'
2019-02-26 14:15:13.074 9224-9224/? A/DEBUG: ABI: 'arm'
2019-02-26 14:15:13.074 9224-9224/? A/DEBUG: pid: 9158, tid: 9209, name: QtThread >>> ch.opengis.qfield <<<
2019-02-26 14:15:13.074 9224-9224/? A/DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
2019-02-26 14:15:13.074 9224-9224/? A/DEBUG: Cause: null pointer dereference
2019-02-26 14:15:13.074 9224-9224/? A/DEBUG: r0 00000000 r1 8dc54908 r2 00002ae8 r3 00000000
2019-02-26 14:15:13.074 9224-9224/? A/DEBUG: r4 00002b68 r5 000118c8 r6 8f37ada8 r7 00002b68
2019-02-26 14:15:13.074 9224-9224/? A/DEBUG: r8 c85efd09 r9 47535542 sl 00000001 fp 88a3c6c0
2019-02-26 14:15:13.074 9224-9224/? A/DEBUG: ip c8666338 sp bfcfc068 lr c85f687d pc eb4fcf6c cpsr 20070010
2019-02-26 14:15:13.075 9224-9224/? A/DEBUG: backtrace:
2019-02-26 14:15:13.075 9224-9224/? A/DEBUG: #00 pc 00018f6c /system/lib/libc.so (memcpy+108)
2019-02-26 14:15:13.075 9224-9224/? A/DEBUG: #1 pc 00032879 /data/data/ch.opengis.qfield/qt-reserved-files/plugins/platforms/android/libqtforandroid.so
but unfortunately it's not immediately visible what's the problem.
Can you try the latest builds (download apk here
<https://download.opengis.ch/qfield/ci-builds/qfield-dev--8b495ad55fbe9a39eb3327d939c3b513164b68c0-armv7.apk>
)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#489 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AttykS5G4ukt8OQTk0VZ1UG45Z8nmOmfks5vRUyLgaJpZM4bOYIU>
.
--
|
|
Strange. Can you send us the project? |
|
Done by mail. I tried with another device (Honor 10), android 9. I cannot crash it but map turns black. GUI is still active and visible. |
|
After some tests, I've done a simple project with light data et it is working well without any crash. Think my working data is involved is the problem. Where would I start looking for ? Could you have a look at the data ? |
|
Hi there |
|
Problem solved. One of my layers was corrupted or something like that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just changed my device from a huawei p9 lite to a samsung a8, android 8.0.0.
On the first, my projects used to work fine, on the second, Qfield crashes when I pan the map.
Reproduction Steps:
Screenshots and GIFs
https://www.noelshack.com/2019-08-7-1550991006-20190224-074627.gif
Qfield version 1.0.0rc3
Additional information:
Files on demand in private message.
The text was updated successfully, but these errors were encountered: