Memory leak found is very hard to track down disappointed kotlinlang #kotlin-native

Channels

kotlin-foundation

compose-android

ohio-kotlin-users

kotlin-by-example

sofl-user-group

kotlin-multiplatform-contest

tricity-kotlin-user-group

kotlin-in-action

android-databinding

cincinnati-user-group

fluid-libraries

codemash-precompiler

kotlingforbeginners

jhipster-kotlin

prozis-android-backup

realworldkotlin

graviton-browser

spring-security

domain-driven-design

connect-audit-events

swiss-user-group

effectivekotlin

refactoring-to-kotlin

russian-kotlinasfirst

androidgithubprojects

introduce-yourself

pocketgitclient

effective-kotlin

algolialibraries

lambdaworld_cadiz

intellij-tricks

kotlin-pakistan

navigation-architecture-component

strife-discord-lib

machinelearningbawas

leedskotlinusergroup

stayhungrystayfoolish

kotest-contributors

practical-functional-programming

swagger-gradle-codegen

100daysofkotlin

kotlinultimatechallenge

pattern-matching

kotlinforbeginners

competitive-programming

compose-ui-showcase

competitivecoding

kotlin-data-storage

skia-wasm-interop-temp

java-to-kotlin-refactoring

event21-community-content

androidx-xprocessing

embedded-kotlin

fb-internal-demo

image-processing

myndocs-oauth2-server

kotlintest-devs

beepiz-libraries

kotlinprogrammers

cscenter-course-2016

k2-early-adopters

intellij-plugins

language-proposals

library-development

refreshversions

language-evolution

kotlinx-datetime

framework-elide

compose-desktop

jvm-ir-backend-feedback

android-architecture

100daysofkotlin-2021

github-workflows-kt

python-contributors

squarelibraries

arrow-contributors

codingconventions

getting-started

Title

i

itnoles

12/08/2017, 7:19 PM

Memory leak found is very hard to track down 😞

o

olonho

12/09/2017, 8:18 AM

Think Valgrind could help here

Compile your program on Linux and just run it with valgrind myprog.kexe

👍 1

i

itnoles

12/09/2017, 6:07 PM

Well, I uses Mac OS X.

it happens in NSURLSession with a delegate or callback.

s

Sam

12/09/2017, 8:16 PM

If you're using a block based wrapper around NSURLSession it can be easy to create a circular reference. The basic delegate callback mechanism of NSURLSession uses a weak reference and should not create a memory leak.

In your block wrapper if the block contains a reference to

this

inside of it, it will create a circular reference. You need to make it a weak reference.

9 Views

#kotlin-native Join Slack