question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

New crash in 1.3.1 on iOS in ReleaseHeapRefStrict

See original GitHub issue

Ktor Version and Engine Used (client or server and name) Common client (HttpClient { … } so default engine) on iOS (arm64) version 1.3.1

Describe the bug Upgrading from 1.3.0 to 1.3.1 introduces a new fatal error which crashes the app, with very little details.

To Reproduce I don’t have a reproducer, but the error really looks like #1380. It somehow happens 100% of the time when my app starts, but not on the first request. Weird.

Screenshots

Main thread when the crash occurs: image Associated line of code: JSON_INDENTED.stringify(JsonElementSerializer, Json.plain.parseJson(maybeJson)) JSON_INDENTED is Json(JsonConfiguration(prettyPrint = true, indent = " ")) maybeJson is a String representation of the received body, which I’m about to log. It’s a custom request Logging feature. Note that I did not change the version of kotlinx.serialization

Thread inside which the crash occurred: image You can see references to ReleaseHeapRefStrict like in #1380.

I also see these logs in 1.3.0, I don’t see them in 1.3.1 and I feel like it crashes before they appear

2020-02-14 15:25:55.352209+0100 MyTarget[4159:1595620] [] tcp_input [C44.1:3] flags=[R] seq=295735571, ack=0, win=0 state=LAST_ACK rcv_nxt=295735571, snd_una=390992163
2020-02-14 15:25:55.354843+0100 MyTarget[4159:1595620] [] tcp_input [C44.1:3] flags=[R] seq=295735571, ack=0, win=0 state=CLOSED rcv_nxt=295735571, snd_una=390992163

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:2
  • Comments:17 (16 by maintainers)

github_iconTop GitHub Comments

4reactions
e5lcommented, Mar 6, 2020

The bug reproduced, and the fix is mostly done. Sorry for the delay.

0reactions
e5lcommented, Mar 20, 2020

The workaround is available in 1.3.2. The proper fix will be possible after the kotlin-native update.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Manage Crash Detection on iPhone 14 models - Apple Support
What is Crash Detection? If your iPhone 14 detects a severe car crash, it can help connect you to emergency services and notify...
Read more >
Road traffic injuries - World Health Organization (WHO)
Every year the lives of approximately 1.3 million people are cut short as a result of a road traffic crash. Between 20 and...
Read more >
How to use Crash Detection on iPhone and Apple Watch
Crash Detection on your iPhone 14, iPhone 14 Pro, Apple Watch SE (2nd generation), Apple Watch Series 8, and Apple Watch Ultra is...
Read more >
Critical Reasons for Crashes Investigated in the National ...
1200 New Jersey Avenue SE., Washington, DC 20590. TRAFFIC SAFETY FACTS. Crash • Stats ... The National Motor Vehicle Crash Causation Survey (NMVCCS),....
Read more >
Apple releases iOS 16.1.2 with Crash Detection improvements
Users can now update their devices to the latest iOS version by going to the Software Update menu within the Settings app. It's...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found