Amy Lee [:amylee] UX Reporter
	Description • 10 years ago

When I take a screenshot from the lockscreen and want to view it by pressing on the actionable notification, the image doesn't always load when I have a previous app opened on my screen. 

Steps to reproduce:
1. It seems to be random when the image doesn't load. Open several apps (contacts, email, gallery, video, music, etc.)
2. Have one app open on the screen and then activate lockscreen
3. Take a screenshot from lockscreen
4. Press the actionable notification to view it. Image doesn't always load.

	John Lu [:mnjul][Please NI or I'll miss]
	Comment 1 • 10 years ago

Greg -- guess this is your call?

	Amy Lee [:amylee] UX Reporter
	Comment 2 • 10 years ago

(In reply to Amy Lee [:amylee] from comment #0)
> Created attachment 8494614 [details]
> 2014-09-24-11-37-21.png
> 
> When I take a screenshot from the lockscreen and want to view it by pressing
> on the actionable notification, the image doesn't always load when I have a
> previous app opened on my screen. 
> 
> Steps to reproduce:
> 1. It seems to be random when the image doesn't load. Open several apps
> (contacts, email, gallery, video, music, etc.)
> 2. Have one app open on the screen and then activate lockscreen
> 3. Take a screenshot from lockscreen
> 4. Press the actionable notification to view it. Image doesn't always load.

If it helps, this issue seems to be common when you have the camera app open and you are opening a screenshot from notifications on lockscreen.

	Gregor Wagner [:gwagner]
	Comment 3 • 10 years ago

What version and memory situation are we talking about here?

	Greg Weng [:snowmantw][:gweng][:λ]
	Comment 4 • 10 years ago

I guess the symptom is: the inline activity showing the image still stick in the previous open app, which I've seen several times. However, as far as I know, this is correct. Because according to Alive, during a much earlier discussion about one irrelevant bug, inline activity belongs to the app is what UX required. So, I'll discuss with Alive, and if this is exactly an UX requirement, either we need to modify the specification to create an exception (or even review  the whole spec to see if this still make sense), or we need to do some tricky things to avoid this happens while remain the same requirement (if the spec still remains the same).

	Greg Weng [:snowmantw][:gweng][:λ]
	Comment 5 • 10 years ago

Of course maybe I'm not correct, that the previous inline activity doesn't affect the later one. So I'll update the result here, after handling this.

	Greg Weng [:snowmantw][:gweng][:λ]
	Comment 6 • 10 years ago

If the way in the vide is correct to reproduce it, I think the possible root cause is what I said. NI Alive to confirm that, or there are some other possible root causes.

	(inactive after 6/18) Alive Kuo [:alive]
	Comment 7 • 10 years ago

* The active app under lockscreen is background. (OOM adj > 2)
* We always render the inline activity in active app even it is not the caller. (We could know by open-app event detail but sometimes it is inaccurate because if the caller is living inside gecko it will be null).
* We may run into comment 4 if the activity is killed following with the camera app by OOM killer and it should not.

But from the attached screenshot, the appWindow seems still there, so I cannot make sure what happens. If comment 4 is true we will not see anything of the view activity.

It will help if we get AppWindow.prototype._DEBUG = true && ActivityWindow.prototype._DEBUG = true && AppWindowManager.DEBUG = true while we reproduce this bug.

Could you try to repro or give Amy a debugging patch to get us the log?

	(inactive after 6/18) Alive Kuo [:alive]
	Comment 8 • 10 years ago

OK, from https://www.youtube.com/watch?v=X3QDsl6tKlE&feature=youtu.be I tend to think this is a gallery issue.

	BMO Automation
	Comment 9 • 6 years ago

Firefox OS is not being worked on