-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Image control crashes on Android when image width exceeds height #32869
Copy link
Copy link
Open
Labels
area-controls-imageImage controlImage controlarea-imageImage loading, sources, cachingImage loading, sources, cachingi/regressionThis issue described a confirmed regression on a currently supported versionThis issue described a confirmed regression on a currently supported versionpartner/syncfusionIssues / PR's with Syncfusion collaborationIssues / PR's with Syncfusion collaborationplatform/androidregressed-in-10-rc2s/triagedIssue has been reviewedIssue has been revieweds/verifiedVerified / Reproducible Issue ready for Engineering TriageVerified / Reproducible Issue ready for Engineering Triaget/bugSomething isn't workingSomething isn't working
Milestone
Metadata
Metadata
Assignees
Labels
area-controls-imageImage controlImage controlarea-imageImage loading, sources, cachingImage loading, sources, cachingi/regressionThis issue described a confirmed regression on a currently supported versionThis issue described a confirmed regression on a currently supported versionpartner/syncfusionIssues / PR's with Syncfusion collaborationIssues / PR's with Syncfusion collaborationplatform/androidregressed-in-10-rc2s/triagedIssue has been reviewedIssue has been revieweds/verifiedVerified / Reproducible Issue ready for Engineering TriageVerified / Reproducible Issue ready for Engineering Triaget/bugSomething isn't workingSomething isn't working
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
Status
In Progress
Description
When using an image that is a lot wider than the height (the example has a dimension of 1600x130, but it also fails on smaller images), the ImageControl throws an exception (Java.Lang.RuntimeException: Canvas: trying to draw too large(322641920bytes) bitmap.) on Android, causing the app to crash.
SfImageEditorBug (2).zip
Steps to Reproduce
Link to public reproduction project repository
No response
Version with bug
9.0.111 SR11.1
Is this a regression from previous behavior?
Not sure, did not test other versions
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
No response
Did you find any workaround?
No response
Relevant log output