Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

Constant Tab crashes on 109.0 (Flatpak or Fedora RPM) when loading bigger contents

  • 12 antwurd
  • 0 hawwe dit probleem
  • 12 werjeftes
  • Lêste antwurd fan Person

more options

I tried the RPM and Flatpak Firefox, both in the newest version give me crashes when Loading Youtube, Invidious, Stud.IP, Nextcloud and more "bigger" sites.

It seems like an OOM error, but I have way enough RAM, 4GB/12GB used.

I tried the Flatpak and the RPM Version.

I tried troubleshooting mode.

I used the Arkenfox user.js on both installs.

Journalctl logs:

https://cloud.uol.de/s/ENY9Dkg7zgQKZZt

https://cloud.uol.de/s/9AyGAibGBnLqG3Y

Operating System: Fedora Linux 37 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.8-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Memory: 11.4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4000

I tried the RPM and Flatpak Firefox, both in the newest version give me crashes when Loading Youtube, Invidious, Stud.IP, Nextcloud and more "bigger" sites. It seems like an OOM error, but I have way enough RAM, 4GB/12GB used. I tried the Flatpak and the RPM Version. I tried troubleshooting mode. I used the Arkenfox user.js on both installs. Journalctl logs: https://cloud.uol.de/s/ENY9Dkg7zgQKZZt https://cloud.uol.de/s/9AyGAibGBnLqG3Y Operating System: Fedora Linux 37 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.8-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Memory: 11.4 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4000

Alle antwurden (12)

more options

Hi

Does Firefox crash if you are not using Arkenfox?

more options

This also happens on a vanilla profile that is generated new and only has GUI settings changed

more options

Wayland... See if you have the same issue in X11. Try downloading Firefox from Mozilla, run firefox-bin from the folder and see if you have the same issue. https://www.mozilla.org/en-US/firefox/all/#product-desktop-release


Operating System: openSUSE Tumbleweed 20230202 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.7-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-4810MQ CPU @ 2.80GHz Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 Manufacturer: Hewlett-Packard Product Name: HP ZBook 17 G2

more options

Shouldnt be a Wayland issue but I try it. X11 is in maintenance mode now and this did not happen before, I use Wayland only since half a year

more options

The same issue happened in the binary too. I let Firefox send a report there.

I tried it with hardware acceleration disabeled, no change

Same behavior on X11

Bewurke troch Person op

more options

Open a bug and provide dev with the data. https://bugzilla.mozilla.org/home

more options

We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.

The crash report is several pages of data. We need the report numbers to see the whole report.

  1. Enter about:crashes in the Firefox address bar and press Enter. A list of Submitted/Unsubmitted Crash Reports will appear, similar to the one shown below.
  2. Copy the 5 most recent Submitted Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.

Note: If a recent Report ID does not start with bp- click on it to submit the report.

(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)

Fx64Beta-aboutcrashes-unsubmitted

Thank you for your help!

More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.

more options

I opened a bug already, may need to add infos.

Edit: Arkenfox disables the Crash reporting out of some reason. But I created a fully vanilla profile and the tabs crashed again, I tried to open "about:crashes" but not existing, not showing in "about:about" too!

The logfile I created through "about:logs" also doesnt seem to contain anything about the crashes, but I opened Reddit.com and added the log down here.

Bewurke troch Person op

more options

``` 2023-02-05 18:52:32.980251 UTC - [Parent 42200: Main Thread]: V/nsHttp 7f7350a77100 called from script: resource://activity-stream/lib/TopSitesFeed.jsm:180:29 2023-02-05 18:52:32.980275 UTC - [Parent 42200: Main Thread]: D/nsHttp NS_CompareLoadInfoAndLoadContext - loadInfo: 0, 0; loadContext: 0, 0. [channel=7f7350a77140] 2023-02-05 18:52:32.980301 UTC - [Parent 42200: Main Thread]: D/nsHttp nsHttpChannel 7f7350a77100 not eligible for tail-blocking 2023-02-05 18:52:32.980320 UTC - [Parent 42200: Main Thread]: D/nsHttp HttpBaseChannel::EnsureRequestContextID this=7f7350a77100 id=a4d80000011b 2023-02-05 18:52:32.980336 UTC - [Parent 42200: Main Thread]: D/nsHttp HttpBaseChannel::AddAsNonTailRequest this=7f7350a77100, rc=7f735c4c6190, already added=0 2023-02-05 18:52:32.980356 UTC - [Parent 42200: Main Thread]: D/nsHttp nsHttpHandler::NotifyObservers [chan=7f7350a77140 event="http-on-opening-request"] 2023-02-05 18:52:32.980389 UTC - [Parent 42200: Main Thread]: D/nsHttp nsHttpChannel::ResolveProxy [this=7f7350a77100] 2023-02-05 18:52:32.980571 UTC - [Parent 42200: Main Thread]: D/nsHttp nsHttpChannel::OnProxyAvailable [this=7f7350a77100 pi=0 status=0 mStatus=0] 2023-02-05 18:52:32.980589 UTC - [Parent 42200: Main Thread]: D/nsHttp nsHttpChannel::BeginConnect [this=7f7350a77100] 2023-02-05 18:52:32.980605 UTC - [Parent 42200: Main Thread]: D/nsHttp host=contile.services.mozilla.com port=-1 2023-02-05 18:52:32.980617 UTC - [Parent 42200: Main Thread]: D/nsHttp uri=https://contile.services.mozilla.com/v1/tiles 2023-02-05 18:52:32.980645 UTC - [Parent 42200: Main Thread]: V/nsHttp Init nsHttpConnectionInfo @7f7350a13200 2023-02-05 18:52:32.980674 UTC - [Parent 42200: Main Thread]: D/nsHttp AltSvcCache::LookupMapping 7f73712766a0 https:contile.services.mozilla.com:443:.::3 2023-02-05 18:52:32.980692 UTC - [Parent 42200: Main Thread]: D/nsHttp AltSvcCache::LookupMapping 7f73712766a0 MISS 2023-02-05 18:52:32.980708 UTC - [Parent 42200: Main Thread]: D/nsHttp AltSvcCache::GetAltServiceMapping 7f73712766a0 key=https:contile.services.mozilla.com:443:.::3 existing=0 validated=0 ttl=0 2023-02-05 18:52:32.980724 UTC - [Parent 42200: Main Thread]: D/nsHttp AltSvcCache::LookupMapping 7f73712766a0 https:contile.services.mozilla.com:443:.::. 2023-02-05 18:52:32.980739 UTC - [Parent 42200: Main Thread]: D/nsHttp AltSvcCache::LookupMapping 7f73712766a0 MISS 2023-02-05 18:52:32.980755 UTC - [Parent 42200: Main Thread]: D/nsHttp AltSvcCache::GetAltServiceMapping 7f73712766a0 key=https:contile.services.mozilla.com:443:.::. existing=0 validated=0 ttl=0 2023-02-05 18:52:32.980768 UTC - [Parent 42200: Main Thread]: D/nsHttp nsHttpChannel 7f7350a77100 Using default connection info 2023-02-05 18:52:32.980795 UTC - [Parent 42200: Main Thread]: D/nsHttp nsHttpChannelAuthProvider::AddAuthorizationHeaders? [this=7f7350a3c700 channel=7f7350a77700] 2023-02-05 18:52:32.980809 UTC - [Parent 42200: Main Thread]: D/nsHttp Skipping Authorization header for anonymous load 2023-02-05 18:52:32.980847 UTC - [Parent 42200: Main Thread]: D/nsHttp nsHttpChannel::MaybeStartDNSPrefetch [this=7f7350a77100, strategy=1] prefetching 2023-02-05 18:52:32.980892 UTC - [Parent 42200: Main Thread]: D/nsHostResolver Resolving host [contile.services.mozilla.com]<> type 0. [this=7f739722deb0] 2023-02-05 18:52:32.980923 UTC - [Parent 42200: Main Thread]: D/nsHostResolver No usable record in cache for host [contile.services.mozilla.com] type 0. 2023-02-05 18:52:32.980937 UTC - [Parent 42200: Main Thread]: D/nsHostResolver NameLookup host:contile.services.mozilla.com af:0 2023-02-05 18:52:32.980954 UTC - [Parent 42200: Main Thread]: D/nsHostResolver NameLookup: contile.services.mozilla.com effectiveTRRmode: 1 flags: 10 2023-02-05 18:52:32.980968 UTC - [Parent 42200: Main Thread]: D/nsHostResolver TRR service not enabled - off or disabled 2023-02-05 18:52:32.980984 UTC - [Parent 42200: Main Thread]: D/nsHostResolver NativeLookup host:contile.services.mozilla.com af:0 2023-02-05 18:52:32.981015 UTC - [Parent 42200: Main Thread]: D/nsHostResolver DNS thread counters: total=3 any-live=0 idle=3 pending=1 2023-02-05 18:52:32.981055 UTC - [Parent 42200: Main Thread]: D/nsHostResolver DNS lookup for host [contile.services.mozilla.com] blocking pending 'getaddrinfo' or trr query: callback [7f735acbb880] 2023-02-05 18:52:32.981076 UTC - [Parent 42200: Main Thread]: D/nsHttp nsHttpChannel::PrepareToConnect [this=7f7350a77100] 2023-02-05 18:52:32.981090 UTC - [Parent 42200: Main Thread]: D/nsHttp nsHttpHandler::NotifyObservers [chan=7f7350a77140 event="http-on-modify-request-before-cookies"] 2023-02-05 18:52:32.981098 UTC - [Parent 42200: DNS Resolver #11]: E/nsHostResolver DNS lookup thread - Calling getaddrinfo for host [contile.services.mozilla.com]. 2023-02-05 18:52:32.981110 UTC - [Parent 42200: Main Thread]: D/nsHttp nsHttpHandler::NotifyObservers [chan=7f7350a77140 event="http-on-modify-request"] 2023-02-05 18:52:32.981522 UTC - [Parent 42200: Main Thread]: D/nsHttp HttpBaseChannel::SetRequestHeader [this=7f7350a77100 header="Sec-Fetch-Dest" value="empty" merge=0] 2023-02-05 18:52:32.981555 UTC - [Parent 42200: Main Thread]: D/nsHttp HttpBaseChannel::SetRequestHeader [this=7f7350a77100 header="Sec-Fetch-Mode" value="cors" merge=0] 2023-02-05 18:52:32.981585 UTC - [Parent 42200: Main Thread]: D/nsHttp HttpBaseChannel::SetRequestHeader [this=7f7350a77100 header="Sec-Fetch-Site" value="cross-site" merge=0] 2023-02-05 18:52:32.981608 UTC - [Parent 42200: Main Thread]: D/nsHttp nsHttpChannel::ContinueOnBeforeConnect [this=7f7350a77100 aShouldUpgrade=0 rv=0] 2023-02-05 18:52:32.981630 UTC - [Parent 42200: Main Thread]: D/nsHttp nsHttpHandler::NotifyObservers [chan=7f7350a77140 event="http-on-before-connect"] 2023-02-05 18:52:32.981873 UTC - [Parent 42200: Main Thread]: D/nsHttp nsHttpChannel::Connect [this=7f7350a77100] 2023-02-05 18:52:32.981903 UTC - [Parent 42200: Main Thread]: D/nsHttp nsHttpChannel 7f7350a77100 tracking resource=0, cos=0, inc=0 2023-02-05 18:52:32.981919 UTC - [Parent 42200: Main Thread]: D/nsHttp nsHttpChannel 7f7350a77100 not eligible for tail-blocking 2023-02-05 18:52:32.981935 UTC - [Parent 42200: Main Thread]: D/nsHttp HttpBaseChannel::AddAsNonTailRequest this=7f7350a77100, rc=7f735c4c6190, already added=1 2023-02-05 18:52:32.981950 UTC - [Parent 42200: Main Thread]: D/nsHttp nsHttpChannel::ConnectOnTailUnblock [this=7f7350a77100] 2023-02-05 18:52:32.981973 UTC - [Parent 42200: Main Thread]: V/nsHttp Init nsHttpConnectionInfo @7f7350ab54d0 2023-02-05 18:52:32.982004 UTC - [Parent 42200: Main Thread]: V/nsHttp nsHttpConnectionMgr::SpeculativeConnect [ci=.SA.......[tlsflags0x00000000]contile.services.mozilla.com:443] 2023-02-05 18:52:32.982076 UTC - [Parent 42200: Main Thread]: D/nsSocketTransport STS dispatch [7f735205fcc0] 2023-02-05 18:52:32.982099 UTC - [Parent 42200: Main Thread]: D/nsSocketTransport PollableEvent::Signal 2023-02-05 18:52:32.982115 UTC - [Parent 42200: Main Thread]: D/nsSocketTransport PollableEvent::MarkFirstSignalTimestamp 2023-02-05 18:52:32.982144 UTC - [Parent 42200: Main Thread]: D/nsSocketTransport PollableEvent::Signal PR_Write 1 2023-02-05 18:52:32.982176 UTC - [Parent 42200: Main Thread]: D/nsHttp nsHttpChannel::OpenCacheEntry [this=7f7350a77100] 2023-02-05 18:52:32.982196 UTC - [Parent 42200: Socket Thread]: D/nsSocketTransport ...returned after 7267 milliseconds 2023-02-05 18:52:32.982223 UTC - [Parent 42200: Socket Thread]: D/nsSocketTransport SocketContext::TimeoutIn socket=7f735bbd0c00, timeout=65535s 2023-02-05 18:52:32.982252 UTC - [Parent 42200: Socket Thread]: D/nsSocketTransport not engaged 2023-02-05 18:52:32.982224 UTC - [Parent 42200: Main Thread]: D/cache2 CacheStorageService::GetCacheIndexEntryAttrs [uri=https://contile.services.mozilla.com/v1/tiles, eid=, contextKey=a,] 2023-02-05 18:52:32.982286 UTC - [Parent 42200: Main Thread]: D/cache2 CacheIndex::HasEntry() [key=a,:https://contile.services.mozilla.com/v1/tiles] 2023-02-05 18:52:32.982293 UTC - [Parent 42200: Socket Thread]: D/nsSocketTransport SocketContext::TimeoutIn socket=7f735d4bc000, timeout=65535s 2023-02-05 18:52:32.982341 UTC - [Parent 42200: Socket Thread]: D/nsSocketTransport not engaged 2023-02-05 18:52:32.982317 UTC - [Parent 42200: Main Thread]: D/cache2 CacheIndex::HasEntry() - result is 0 2023-02-05 18:52:32.982378 UTC - [Parent 42200: Socket Thread]: D/nsSocketTransport SocketContext::TimeoutIn socket=7f735d4c0800, timeout=65535s 2023-02-05 18:52:32.982398 UTC - [Parent 42200: Socket Thread]: D/nsSocketTransport not engaged 2023-02-05 18:52:32.982383 UTC - [Parent 42200: Main Thread]: D/cache2 CachePerfStats::IsCacheSlow() - result is slow based on perf type 0 [avgShort=516, avgLong=155, stddevLong=28] 2023-02-05 18:52:32.982413 UTC - [Parent 42200: Socket Thread]: D/nsSocketTransport SocketContext::TimeoutIn ```

more options

Try to start Firefox via a terminal window to see if that gives some extra info,

more options

Update:

109.0.1 for Fedora still crashes

109.0.1 Flatpak works normally

Bewurke troch Person op

more options

cor-el said

Try to start Firefox via a terminal window to see if that gives some extra info,

running the flatpak from terminal with "--verbose" gives no extra output

RPM feedback:

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: No GPUs detected via PCI (t=4.50074) [GFX1-]: No GPUs detected via PCI Crash Annotation GraphicsCriticalError: |[0][GFX1-]: No GPUs detected via PCI (t=4.50074) |[1][GFX1-]: glxtest: process failed (received signal 11) (t=4.50092) [GFX1-]: glxtest: process failed (received signal 11) fatal allocator error: invalid uninitialized allocator usage Redirecting call to abort() to mozalloc_abort

Bewurke troch Person op