Chủ đề này đã được lưu trữ. Vui lòng hỏi một câu hỏi mới nếu bạn cần giúp đỡ.
firefox 22 keeps crashing
bp-51be9f9b-c8d8-455a-b8ea-e70072130723 bp-8e5327a5-0523-42af-ab49-374a72130723 bp-ea6e0da5-2757-4b2a-b107-cb62d2130723
I use ffox with 100 tabs open, it crashes once per 2hours or so, sometimes faster...
I have tried almost everything...
I have used addons like MEMORY FOX, UNLOAD TAB, but no solution...
all extensions updated, all plugins updated....
thanks for any help...
Được chỉnh sửa bởi Jota vào
Tất cả các câu trả lời (20)
That could be a problem with the Flash plugin or plugin-container process.
You can check for problems with current Flash plugin versions and try these:
- disable a possible RealPlayer Browser Record Plugin extension for Firefox and update the RealPlayer if installed
- disable protected mode in the Flash plugin (Flash 11.3+ on Windows Vista and later)
- disable hardware acceleration in the Flash plugin
thanks cor-el, i will try a workaround with flash and post the results here... thx
Được chỉnh sửa bởi Jota vào
i did this:
disable a possible RealPlayer Browser Record Plugin extension for Firefox and update the RealPlayer if installed disable protected mode in the Flash plugin (Flash 11.3+ on Windows Vista and later)
but still is crashing out of nowere...
when is not ffox is the plugin container.....
i cant understand whats so wrong... i have read people on forums using ffox with 4g ram and 500 tabs without problems...
and for me here is a never ending crash spree...
thanks for any help....
Does it help if you disable the JIT compiler?
Try to disable the ionmonkey JIT compiler by setting these jit prefs to false on the about:config page (Search: jit) to see if that helps.
trying it now, lets see what happens....
still crashing... it took more time this time, seems to crash when i move fast between tabs...
the plugin container https://crash-stats.mozilla.com/report/index/bc99c2ee-c5eb-44b9-b8f2-fc1382131021
and another one out of nowere:
That are crashes with mozalloc_abort, so it looks that something goes wrong with allocating memory.
This last crash has a System Memory Use Percentage: 86, so maybe you need to increase thee page file.
thx... i tried, but it keeps going the crashing course: https://crash-stats.mozilla.com/report/index/3b28373c-2318-44ec-a351-6e2072131022
more CRASH test dummies..
i dont know what to do... is really a nightmare for me :((((
oh god... neverending https://crash-stats.mozilla.com/report/index/36ff234c-e9a6-4a3c-b302-a93972131023
now im also having weird errors.... like twitter malfunctions.... drag and drop on twitter is not working for me, the rollover menu either...
when i try to save a session with session manager i get an error:
This operation failed due to a file access error: 'out of memory' when calling method: [nsISessionStore::getBrowserState]
Được chỉnh sửa bởi Jota vào
Unfortunately those linked crash reports have an [@ EMPTY] signature, so there is no data available that would make it possible to tell something about the cause of the crash.
Do you have submitted crash reports with a "bp-" prefix that show a crashing thread?
Create a new profile as a test to check if your current profile is causing the problems.
See "Creating a profile":
If the new profile works then you can transfer some files from an existing profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over the problem.
Do a malware check with some malware scanning programs on the Windows computer.
Please scan with all programs because each program detects different malware.
All these programs have free versions.
Make sure that you update each program to get the latest version of their databases before doing a scan.
- Malwarebytes' Anti-Malware:
- Microsoft Safety Scanner:
- Windows Defender: Home Page:
- Spybot Search & Destroy:
- Kasperky Free Security Scan:
You can also do a check for a rootkit infection with TDSSKiller.
- Anti-rootkit utility TDSSKiller:
- "Spyware on Windows": http://kb.mozillazine.org/Popups_not_blocked
i have tested for malware and the system seems to be clean.
I dont understand this: "Do you have submitted crash reports with a "bp-" prefix that show a crashing thread?"
i will read about the new profile, but as i use ffox for work, and i need to have near 250 tabs always open is hard for me to move it all and test...
for some reason ALL of the latest crashes are:
[@ EMPTY: no crashing thread identified; corrupt dump ]
Wow, 250 tabs. Are those generally the same sites or do you have to visit a lot of new sites? The reason I ask is that you might consider using NoScript to block extraneous scripts from loading. It does require training, i.e., checking the list of blocked servers when you view a page and approving the ones that should run, sometimes in two or three rounds, so the more new sites you visit the more time it will take.
hello jscher2000, thx for your reply, yes, lets say 80% same sites, 20% new ones, sometimes i get that "unresponsive script" message too... but in front of the everyday crashes thats a minor problem...
im getting firefox crashes with empty threads in the reports, but the plugin container crashes always look the same:
Nombre del evento de problema: APPCRASH Nombre de la aplicación: plugin-container.exe Versión de la aplicación: 18.104.22.16846 Marca de tiempo de la aplicación: 526b1daa Nombre del módulo con errores: mozalloc.dll Versión del módulo con errores: 22.214.171.12446 Marca de tiempo del módulo con errores: 526af0bc Código de excepción: 80000003 Desplazamiento de excepción: 0000119c Versión del sistema operativo: 6.1.7600.2.0.0.256.1 Id. de configuración regional: 3082 Información adicional 1: 0a9e Información adicional 2: 0a9e372d3b4ad19135b953a78882e789 Información adicional 3: 0a9e Información adicional 4: 0a9e372d3b4ad19135b953a78882e789
this crash (i got one per hour or so) seem to be not-empty: