Bug 694568 - out of memoryerr in mupdf 1.3
Summary: out of memoryerr in mupdf 1.3
Status: RESOLVED FIXED
Alias: None
Product: MuPDF
Classification: Unclassified
Component: mupdf (show other bugs)
Version: unspecified
Hardware: Android Phone Android
: P4 normal
Assignee: Paul Gardiner
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-03 20:02 UTC by Jayson
Modified: 2014-06-18 03:50 UTC (History)
2 users (show)

See Also:
Customer:
Word Size: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jayson 2013-09-03 20:02:51 UTC
When I frequently zoom one page ,maybe the program creates too much bitmap,it crashes.The report is as follows:
       09-04 11:01:28.472: E/AndroidRuntime(17496): FATAL EXCEPTION: AsyncTask #5
09-04 11:01:28.472: E/AndroidRuntime(17496): java.lang.RuntimeException: An error occured while executing doInBackground()
09-04 11:01:28.472: E/AndroidRuntime(17496): 	at com.artifex.mupdfdemo.AsyncTask$3.done(AsyncTask.java:304)
09-04 11:01:28.472: E/AndroidRuntime(17496): 	at java.util.concurrent.FutureTask$Sync.innerSetException(FutureTask.java:273)
09-04 11:01:28.472: E/AndroidRuntime(17496): 	at java.util.concurrent.FutureTask.setException(FutureTask.java:124)
09-04 11:01:28.472: E/AndroidRuntime(17496): 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:307)
09-04 11:01:28.472: E/AndroidRuntime(17496): 	at java.util.concurrent.FutureTask.run(FutureTask.java:137)
09-04 11:01:28.472: E/AndroidRuntime(17496): 	at com.artifex.mupdfdemo.AsyncTask$SerialExecutor$1.run(AsyncTask.java:233)
09-04 11:01:28.472: E/AndroidRuntime(17496): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
09-04 11:01:28.472: E/AndroidRuntime(17496): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
09-04 11:01:28.472: E/AndroidRuntime(17496): 	at java.lang.Thread.run(Thread.java:856)
09-04 11:01:28.472: E/AndroidRuntime(17496): Caused by: java.lang.OutOfMemoryError
09-04 11:01:28.472: E/AndroidRuntime(17496): 	at android.graphics.Bitmap.nativeCreate(Native Method)
09-04 11:01:28.472: E/AndroidRuntime(17496): 	at android.graphics.Bitmap.createBitmap(Bitmap.java:640)
09-04 11:01:28.472: E/AndroidRuntime(17496): 	at android.graphics.Bitmap.createBitmap(Bitmap.java:620)
09-04 11:01:28.472: E/AndroidRuntime(17496): 	at com.artifex.mupdfdemo.MuPDFCore.drawPage(MuPDFCore.java:165)
09-04 11:01:28.472: E/AndroidRuntime(17496): 	at com.artifex.mupdfdemo.MuPDFPageView.drawPage(MuPDFPageView.java:405)
09-04 11:01:28.472: E/AndroidRuntime(17496): 	at com.artifex.mupdfdemo.PageView$2.doInBackground(PageView.java:324)
09-04 11:01:28.472: E/AndroidRuntime(17496): 	at com.artifex.mupdfdemo.PageView$2.doInBackground(PageView.java:1)
09-04 11:01:28.472: E/AndroidRuntime(17496): 	at com.artifex.mupdfdemo.AsyncTask$2.call(AsyncTask.java:290)
09-04 11:01:28.472: E/AndroidRuntime(17496): 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)
09-04 11:01:28.472: E/AndroidRuntime(17496): 	
What should I do?
Comment 1 Robin Watts 2013-12-30 05:16:47 UTC
Passing to Paul for his comments.

I suspect that in the absence of more information regarding the exact device/software version/file in use he may just close it.
Comment 2 Paul Gardiner 2014-01-02 07:29:28 UTC
I wonder what version of MuPDF this is. We no longer reallocate bitmaps, so I'd be surprised at this happening when using the current tip of master from the git repository.
Comment 3 Matt Holgate 2014-06-18 03:50:45 UTC
We believe this is already fixed; without additional info as to the version of mupdf that was in use, it's difficult to be certain.