Dictation memory leak

Watchapp Development
1

Using the dictation service in an app causes a 36 byte memory leak on every transcription request. Has anyone dealt with this in the past and come up with a way to reclaim that memory?

Losing 900B of memory per 25 transcriptions is pretty bad since there will be a peer-to-peer messaging system in my app, and i’m already low on memory (it took a lot of optimizing just to get the dictation service to fit)

1 Like
2

Hm, is that maybe the chunk of memory allocated for the text returned by dictation?

1 Like
3

I was wondering that, but it’s always 36 bytes regardless of message length. I also tried:

  • Doing a dummy callback from transcription (to rule out my own code)
  • Statically defining the dictation object
  • dynamically allocating the dictation object

I did notice that if I terminate the dictation session before the internal text result window pops up, there is no leaked memory. I’ll take a look at the SDK and see if there’s something in there. (I have no experience with building the SDK so lol idk if i’ll get anywhere with that)

1 Like