uazo / cromite

Cromite a Bromite fork with ad blocking and privacy enhancements; take back your browser!
https://www.cromite.org/
GNU General Public License v3.0
3.47k stars 78 forks source link

Android: Failed to import 600 KB bookmark export #1605

Open iyesin opened 3 days ago

iyesin commented 3 days ago

Preliminary checklist

Can the bug be reproduced with corresponding Chromium version?

Yes

Are you sure?

Yes

Cromite version

130.0.6723.67 (Official Build) (64-bit)

Device architecture

arm64-v8a

Platform version

Android 12.1

Android Device model

Motorola edge 20 pro (Lineage 12)

Is the device rooted?

Yes

Changed flags

no flags changed

Is this bug happening ONLY in an incognito tab?

No

Is this bug caused by the adblocker?

No

Is this bug a crash?

No

Describe the bug

I have a (kinda) big bookmarks.html export - 620 KiB. It is from the past Bromite installation. When I'm attempting to import this file to bookmarks in Cromite, it fails to do that with a toast message, saying

Unable to complete previous operation due to low memory

I believe, my 12GB RAM device have enough RAM to parse 620 KiB of simple HTML file.

Steps to reproduce the bug

  1. Download attached bookmarks.zip file, unzip it and upload it on your phone.
  2. Open bookmarks tab (chrome-native://bookmarks/folder/0).
  3. On the right from the title Bookmarks tap '⋮' and select Import.
  4. Select uploaded bookmarks.html.

bookmarks.zip

Expected behavior

All bookmarks successfully imported.

Screenshots

Details

![Screenshot_20241022-210359_Cromite_1](https://github.com/user-attachments/assets/a7981856-4237-417b-984f-86474e2e61ad)

uazo commented 3 days ago

Could you create a test file?

iyesin commented 2 days ago

Hey, @uazo !

Sorry. Initial submission was kinda broken. Here it is.

bookmarks.zip

uazo commented 2 days ago

not reproducible:

image

iyesin commented 1 day ago

I don't get it. It is reproducible on my phone with 100% of cases. Actually this prevents me from importing my bookmarks back. I tried deleting the app and installing it back from F-Droid. No luck there, same result.