Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OsmAnd on IPAD => Permanent crash #63

Closed
SvenHi opened this issue May 27, 2015 · 2 comments
Closed

OsmAnd on IPAD => Permanent crash #63

SvenHi opened this issue May 27, 2015 · 2 comments

Comments

@SvenHi
Copy link

SvenHi commented May 27, 2015

Environment:
IPad 3 64GB
IOS 8
German
Osmand 1.0.222
Installed Charts: German (all), Italian (all), Switz, Austria, Seemarks

Active view: Nautical

After some actions (zoom in/out) the application freezed.
In "taskmanager" (double click home button) i closed osmand.
Try to open again => Wellcome screen appear (white window, small osmand logo) => after ~10 seconds, the application terminates (back to IOS screen).
=> Open taskmanger again => I can see the freezed chart window before.
=> Restart of IPad => Furthermore freezed osmand

=> So it seems there is a possibility that Osmand crashs, and the consequence is permanent.

Probably i have to re- install OSMAND again.

If you are interested, to have more information about this (maybe error logs, etc), please reply.

@SvenHi
Copy link
Author

SvenHi commented May 27, 2015

Log:

Hardware Model: iPad3,3
Process: OsmAnd Maps [334]
Path: /private/var/mobile/Containers/Bundle/Application/32AB3238-327D-48BD-8D42-EBD0CAFD1350/OsmAnd Maps.app/OsmAnd Maps
Identifier: net.osmand.maps
Version: 1.0.222 (1.0.222)
Code Type: ARM (Native)
Parent Process: launchd [1]

Date/Time: 2015-05-27 23:17:06.427 +0200
Launch Time: 2015-05-27 23:16:51.171 +0200
OS Version: iOS 8.3 (12F69)
Report Version: 105

Exception Type: 00000020
Exception Codes: 0x000000008badf00d
Highlighted Thread: 0

Application Specific Information:
<BKNewProcess: 0x1662e5b0; net.osmand.maps; pid: 334; hostpid: -1> has active assertions beyond permitted time:
{(
<BKProcessAssertion: 0x16630a40> id: 42-47C8D037-CB3F-4E4B-94B7-EA42630E7E94 name: Suspending process: <BKNewProcess: 0x1662e5b0; net.osmand.maps; pid: 334; hostpid: -1> permittedBackgroundDuration: 10.000000 reason: suspend owner pid:42 preventSuspend preventThrottleDownCPU preventThrottleDownUI preventSuspendOnSleep
)}

Elapsed total CPU time (seconds): 11.560 (user 11.560, system 0.000), 52% CPU
Elapsed application CPU time (seconds): 1.638, 7% CPU

@vshcherb
Copy link
Member

vshcherb commented Aug 2, 2018

I guess issues is outdated or was already fixed

@vshcherb vshcherb closed this as completed Aug 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants