can't send 100+ tabs from Android
Categories
(Fenix :: Tabs, defect)
Tracking
(Not tracked)
People
(Reporter: dineshbhattrai0, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Android 14; Mobile; rv:133.0) Gecko/133.0 Firefox/133.0
Steps to reproduce:
I sent 100+ tabs from my android.
I often open so many tabs in android from different tabs and don't read them.
When I'm on laptop, I send the tabs from mobile and then read there.
However, that fails when I work with 100+ tabs.
Actual results:
Sending fails. Almost 100 of them get loaded and others don't get sent at all.
If I try again, none or a few get sent. I've been having this issue
for months and seems like there is 24 hour limit or 100 tabs per day.
This artificial limit seems very much limiting.
Expected results:
All the tabs should be sent. Sending shouldn't fail.
Also a more useful error message would be helpful.
|
||
Comment 1•3 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Fenix::Tabs' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 2•3 months ago
|
||
Hey,
Thanks for reporting the bug.
I can reproduce the bug.
STR
- Have Fenix connected to a Firefox Account, and Firefox Desktop connected to the same account
- Use debug drawer to open 101 tabs
- From the Tabs Tray, use "Three dots menu", "share all tabs" and send them to the Fx Desktop instance
Expected result
- All the tabs are opened on Fx Desktop
Actual result
- No tab is sent from mobile to Fx Desktop
- After this failure, sharing any other tab individually will fail and show a snackbar or even crash
|
||
Comment 3•3 months ago
|
||
This is the Fenix equivalent to bug 1817329. However, any crashes should be investigated independently because even in this known case we should not crash. I doubt the crash originates directly from the send-tab code though, but would need to see a stack to be sure.
|
|
||
Comment 4•3 months ago
|
||
Unfortunately I wasn't able to reproduce the crash any more.
But I could get this from about:crashes on my device:
52a423dd-80a4-458e-a9af-f36e9859cce4
java.lang.IllegalStateException: Fragment ShareFragment{5e56731} (ffec53c1-6701-4ce0-a752-e51c9812d3f7) not attached to a context.
----
java.lang.IllegalStateException: Fragment ShareFragment{5e56731} (ffec53c1-6701-4ce0-a752-e51c9812d3f7) not attached to a context.
at androidx.fragment.app.Fragment.requireContext(Fragment.java:18)
at org.mozilla.fenix.ext.FragmentKt.getRequireComponents(Fragment.kt:6)
at org.mozilla.fenix.share.ShareFragment.consumePrompt(ShareFragment.kt:1)
at org.mozilla.fenix.share.ShareFragment$onCreateView$1.invoke(ShareFragment.kt:15)
at org.mozilla.fenix.share.DefaultShareController$shareToDevicesWithRetry$1.invokeSuspend(ShareController.kt:114)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:9)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:112)
at android.os.Handler.handleCallback(Handler.java:958)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:230)
at android.os.Looper.loop(Looper.java:319)
at android.app.ActivityThread.main(ActivityThread.java:9063)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:588)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1103)
Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@8e0cb69, Dispatchers.Main]
|
|
||
Comment 5•3 months ago
|
||
Description
•