PeekAndPop
PeekAndPop copied to clipboard
shalskar
Out of memory at PeekAndPop.initialiseViewTreeObserver
Hello shalskar,
I am getting this issue while scrolling listview. I have set peekand pop general listener on long click image of adapter view.
heap: Out of memory on a 9540-byte allocation.
05-17 09:33:27.836 877-877/com.numberatank I/dalvikvm: "main" prio=5 tid=1 RUNNABLE
05-17 09:33:27.836 877-877/com.numberatank I/dalvikvm: | group="main" sCount=0 dsCount=0 obj=0xa62d44b0 self=0xb7bca510
05-17 09:33:27.836 877-877/com.numberatank I/dalvikvm: | sysTid=877 nice=0 sched=0/0 cgrp=[fopen-error:2] handle=-1216674752
05-17 09:33:27.836 877-877/com.numberatank I/dalvikvm: | schedstat=( 7305323441 1221308445 25267 ) utm=586 stm=143 core=0
05-17 09:33:27.836 877-877/com.numberatank I/dalvikvm: at java.util.concurrent.CopyOnWriteArrayList.add(CopyOnWriteArrayList.java:~267)
05-17 09:33:27.856 877-877/com.numberatank I/dalvikvm: at android.view.ViewTreeObserver.addOnGlobalLayoutListener(ViewTreeObserver.java:369)
05-17 09:33:27.856 877-877/com.numberatank I/dalvikvm: at com.numberatank.peekandpop.PeekAndPop.initialiseViewTreeObserver(PeekAndPop.java:168)
05-17 09:33:27.856 877-877/com.numberatank I/dalvikvm: at com.numberatank.peekandpop.PeekAndPop.initialisePeekView(PeekAndPop.java:145)
05-17 09:33:27.856 877-877/com.numberatank I/dalvikvm: at com.numberatank.peekandpop.PeekAndPop.init(PeekAndPop.java:111)
05-17 09:33:27.856 877-877/com.numberatank I/dalvikvm: at com.numberatank.peekandpop.PeekAndPop.
Hmmm, I'm not sure if this OOM is being caused by the PeekAndPop library, however if you have your code here on Github I can pull it down and check it out if you'd like?
I am working on product so douldn't share project but I am sharing peekand pop uses code here. I have used this code in my adapter
final PeekAndPop peekAndPop = new PeekAndPop.Builder(fragment.getActivity()) .blurBackground(true) .peekLayout(R.layout.peek_view)
.parentViewGroupToDisallowTouchEvents(channelListview) .build();
peekAndPop.addLongClickView(viewHolder.imageView, position);
peekAndPop.setOnGeneralActionListener(new
PeekAndPop.OnGeneralActionListener() { @Override public void onPeek(View longClickView, int position) { LogUtils.e("", "onPeek::");
final ImageView imageView = (ImageView)
peekAndPop.getPeekView().findViewById(R.id.imageView); final ProgressWheel progressWheel = (ProgressWheel) peekAndPop.getPeekView().findViewById(R.id.progress_wheel); if (!TextUtils.isEmpty(imgChannelid) && imgChannelid.equals(channelid)) { Picasso.with(context) .load(Uri.fromFile(new File(context.getCacheDir(), "channelLarge"))) .into(imageView); } else { final String url = Constants.CHANNEL_IMAGE_URL
- channelid + "/fs_" + img; // Utils.showWhiteProgressDialog(context); progressWheel.setVisibility(View.VISIBLE); Picasso.with(context) .load(url) .into(imageView, new com.squareup.picasso.Callback() { @Override public void onSuccess() { // Utils.closeProgressDialog();
progressWheel.setVisibility(View.GONE); }
@Override
public void onError() {
// Utils.closeProgressDialog();
progressWheel.setVisibility(View.GONE); Picasso.with(context) .load(url)
.placeholder(R.drawable.profilepic) .into(imageView); } }); } }
@Override
public void onPop(View longClickView, int position) {
LogUtils.e("", "onPop::");
}
});
}
On Wed, May 18, 2016 at 12:13 PM, Vincent Te Tau [email protected] wrote:
Hmmm, I'm not sure if this OOM is being caused by the PeekAndPop library, however if you have your code here on Github I can pull it down and check it out if you'd like?
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/shalskar/PeekAndPop/issues/13#issuecomment-219939159
Thanks & Regards,
*Jiten Ramoliya *
How large are your image files? I would suspect your problem lies there and not with the PeekAndPop library.
My image size is 11kb. 12-15 images available in adapter
On Wed, May 18, 2016 at 12:38 PM, Vincent Te Tau [email protected] wrote:
How large are your image files? I would suspect your problem lies there and not with the PeekAndPop library.
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/shalskar/PeekAndPop/issues/13#issuecomment-219943906
Thanks & Regards,
*Jiten Ramoliya *
Strange, those images don't seem to be terribly large. Does this crash occur consistently at the same point? It might pay to do a memory heap dump before it crashes to see where your memory is allocated.
Yes Its occuring every time from same point. Its always come from PeekAndPop.initialiseViewTreeObserver
Yes, It crash from same point.
On Wed, May 18, 2016 at 12:45 PM, Vincent Te Tau [email protected] wrote:
Strange, those images don't seem to be terribly large. Does this crash occur consistently at the same point? It might pay to do a memory heap dump before it crashes to see where your memory is allocated.
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/shalskar/PeekAndPop/issues/13#issuecomment-219945289
Thanks & Regards,
*Jiten Ramoliya *
I'm still not sure if the library is causing this OOM. It's probable that you have a memory leak somewhere and that the library is simply the hitting the limit of memory by coincidence. I will have a look into it but it may be quite hard to replicate it without a bit more background as to what's happening in your app.
It might pay to have a look at your allocated memory before clicking on the peek view.
Ok, Let me check. I will know you
On Sat, May 21, 2016 at 4:40 PM, Vincent Te Tau [email protected] wrote:
I'm still not sure if the library is causing this OOM. It's probable that you have a memory leak somewhere and that the library is simply the hitting the limit of memory by coincidence. I will have a look into it but it may be quite hard to replicate it without a bit more background as to what's happening in your app.
It might pay to have a look at your allocated memory before clicking on the peek view.
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/shalskar/PeekAndPop/issues/13#issuecomment-220772074
Thanks & Regards,
*Jiten Ramoliya *
I'm assuming you're using Android Studio, in the android panel (where logcat is located), click on memory tab. This will show you a graph of memory allocation in your app, to the left there is an icon called "Dump Java Heap" which allows you to get a snapshot of memory allocation at that particular point.
In this snapshot you should be able to see where where exactly your memory is allocated and what may be causing the OOM.