Home/ Questions/Q 8268777
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-08T06:00:41+00:00

I read somewhere that broadcast receiver runs in a separate process than the app,

  • 0

I read somewhere that broadcast receiver runs in a separate process than the app, and because of this it has an own heap. Now if in the broadcast receiver I start an activity from my app, will this be running in the app’s process or still in the process of the broadcast receiver?

Is the answer of this question also true for native heap (pre-honeycomb API)?.

Wondering because I have to start a memory expensive activity / screen when I receive a push notification, and if I’m in the middle of some other memory expensive activity, in the app, it will probably cause an out of memory error. But if it’s a separate heap (more specifically – native heap, since the memory consumption comes from bitmaps and I’m developing for API pre-honeycomb) I don’t have to worry about it.

Note “read somewhere” refers to: Why so much memory?
Nikolay Chorniy’s post

“There is a tricky workaround which I used to avoid OutOfMemoryError. I registered a receiver so that it ran on different process…”

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I read somewhere that broadcast receiver runs in a separate process than the app

    All components run in the same process by default.

    Wondering because I have to start a memory expensive activity / screen when I receive a push notification

    The user may not necessarily appreciate you displaying “a memory expensive activity / screen” in the middle of nowhere.

    • 0