Closed Bug 656494 Opened 14 years ago Closed 14 years ago

Lots of crashing [@ WrappedNativeProtoMarker ] [@ nsXPConnect::Traverse ]

Categories

(Firefox :: General, defect)

4.0 Branch
x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: allenjohnson, Unassigned)

References

Details

(Keywords: crash)

Crash Data

User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0.1) Gecko/20110429 Firefox/4.0.1 Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0.1) Gecko/20110429 Firefox/4.0.1 On Linux from time to time firefox will become very unstable. It happens with or without extensions. I may have narrowed it down to after I have torrented something. For example yesterday I downloaded a new Linux distro and it is crashing quite a bit today. It is not exclusively tied to a distro. It's not exclusively tied to a plugin. It just starts crashing a whole lot from time to time. If I start it in the terminal it only says "segmentation fault" when it crashes. Restarting helps sometimes, but when it's happening it'll usually start up either right away after restarting, or it'll hold off before it starts doing it again. Reproducible: Always Steps to Reproduce: 1.torrent? 2.start firefox in linux 3.lots of crashing commences Actual Results: I don't really want to *try* to reproduce this, because I'm pretty sure it'll get worse if I use torrents. It last crashed when I started filling out this bug report. This may just be a problem with my hardware and/or Linux. I'm not sure how common this is.
Please post the related crash IDs from about:crashes. https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report Does the issue still occur if you start Firefox in Safe Mode? https://support.mozilla.com/en-US/kb/Safe+Mode How about with a new, empty profile? https://support.mozilla.com/en-US/kb/Basic+Troubleshooting#w_8-make-a-new-profile
Keywords: stackwanted
Version: unspecified → 4.0 Branch
Is there a way to get the IDs for Firefox 4? For what it's worth this would happen in Firefox 3 as well and I would always send in the report.
I thought I would add that I've done as much as install a completely new distro of Linux and a clean install of Firefox without installing anything (including flash), and it still crashed. The amount it crashes varies, but sometimes it will clearly want to crash over and over and there's no way to stop it. I can restart, reinstall everything, etc...
(In reply to comment #2) > Is there a way to get the IDs for Firefox 4? Yes, enter about:crashes in the location bar and the copy the Report IDs that are related to this bug and paste them here. Even if you crash different versions of Firefox they will all shown be together in about:crashes. But just post crash IDs that are related to the bug, otherwise that may cause some confusion. The date and time in the right column helps you with that. This link describes how to do it, but it isn't harder than just copy the relevant IDs from about crashes and paste them in the bug. https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report
There isn't an about:crashes in Firefox 4. It's been crashing again on my main install as well as a Live CD I was using earlier.
Alright, my bad. The version of Firefox I had was compiled with crash reports disabled. The first couple times it crashed with the official binary it said the english dictionary crashed the system. I uninstalled it. Here are the other two which occured in the last 10 minutes or so: https://crash-stats.mozilla.com/report/index/13be4eb2-aed9-4754-85d7-bc5662110516 https://crash-stats.mozilla.com/report/index/69a2a612-152e-40e2-b16b-aa16d2110516
0 libxul.so WrappedNativeProtoMarker js/src/xpconnect/src/xpcprivate.h:1930 1 libxul.so JS_DHashTableEnumerate js/src/jsdhash.cpp:743 2 libxul.so XPCWrappedNativeScope::MarkAllWrappedNativesAndProtos js/src/xpconnect/src/xpcmaps.h:388 3 libxul.so XPCJSRuntime::GCCallback js/src/xpconnect/src/xpcjsruntime.cpp:741 4 libxul.so DOMGCCallback dom/base/nsJSEnvironment.cpp:3500 5 libxul.so js_GC js/src/jsgc.cpp:2514 6 libxul.so JS_GC js/src/jsapi.cpp:2662 7 libxul.so nsXPConnect::Collect js/src/xpconnect/src/nsXPConnect.cpp:405 8 libxul.so nsXPConnect::GarbageCollect js/src/xpconnect/src/nsXPConnect.cpp:413 9 libxul.so nsJSContext::GarbageCollectNow dom/base/nsJSEnvironment.cpp:3271 10 libxul.so nsTimerImpl::Fire xpcom/threads/nsTimerImpl.cpp:425 11 libxul.so nsTimerEvent::Run xpcom/threads/nsTimerImpl.cpp:517 12 libxul.so nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:633 13 libxul.so NS_ProcessNextEvent_P nsThreadUtils.cpp:250 14 libxul.so mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:110 15 libxul.so MessageLoop::RunInternal ipc/chromium/src/base/message_loop.cc:219 16 libxul.so MessageLoop::Run ipc/chromium/src/base/message_loop.cc:202 17 libxul.so nsBaseAppShell::Run widget/src/xpwidgets/nsBaseAppShell.cpp:192 18 libxul.so nsAppStartup::Run toolkit/components/startup/src/nsAppStartup.cpp:220 19 @0xb76dc7b3 20 libxul.so XRE_main toolkit/xre/nsAppRunner.cpp:3786 21 firefox-bin main nsBrowserApp.cpp:158 22 libc-2.13.so libc-2.13.so@0x19102 23 ld-2.13.so ld-2.13.so@0xd91a 24 ld-2.13.so ld-2.13.so@0x1386f 25 libc-2.13.so libc-2.13.so@0x19018 26 firefox-bin Output nsBrowserApp.cpp:77 27 @0x0
Keywords: stackwantedcrash
Summary: Lots of crashing → Lots of crashing [@ WrappedNativeProtoMarker ] [@ nsXPConnect::Traverse ]
0 libxul.so nsXPConnect::Traverse js/src/xpconnect/src/nsXPConnect.cpp:697 1 libxul.so GCGraphBuilder::Traverse xpcom/base/nsCycleCollector.cpp:1523 2 libxul.so nsCycleCollector::MarkRoots xpcom/base/nsCycleCollector.cpp:1764 3 libxul.so nsCycleCollector::BeginCollection xpcom/base/nsCycleCollector.cpp:2633 4 libxul.so nsCycleCollectorRunner::Run xpcom/base/nsCycleCollector.cpp:3321 5 libxul.so nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:633 6 libxul.so NS_ProcessNextEvent_P nsThreadUtils.cpp:250 7 libxul.so nsThread::ThreadFunc xpcom/threads/nsThread.cpp:277 8 libnspr4.so _pt_root ptthread.c:187 9 libpthread-2.13.so libpthread-2.13.so@0x6c76 10 libc-2.13.so libc-2.13.so@0xcfc6d
I was doing some torrenting early this morning. Not sure if this is a coincidence. I've had 10+ crashes in the last few hours. I restart after each couple. bp-ebff91e0-5360-4566-9a04-27f5f2110523 05/23/20110 9:49 AM bp-00990e77-1109-4cf6-8bf9-4c2422110523 05/23/20110 9:46 AM bp-06615837-f8b3-4c90-858c-f355f2110523 05/23/20110 8:49 AM bp-fe501152-8adf-452e-8306-f6e822110523 05/23/20110 8:49 AM 71ba109f-aed9-92e7-7b04a602-6da9de16 05/23/20110 8:14 AM bp-8dceb619-5c99-454b-b0c2-700352110523 05/23/20110 8:06 AM 35a2916e-8520-6258-1452c51d-4299c565 05/23/20110 8:04 AM bp-3139b29d-a4ac-4693-8715-a20cb2110523 05/23/20110 6:04 AM 39cef076-958c-1d42-5d210587-054ac11e 05/23/20110 6:04 AM
Crash Signature: [@ WrappedNativeProtoMarker ] [@ nsXPConnect::Traverse ]
(In reply to comment #6) > Alright, my bad. The version of Firefox I had was compiled with crash > reports disabled. Just to make sure, did you get Firefox from www.mozilla.org, or did you build it yourself? Also, were you able to narrow down the steps to reproduce this so we can verify it too? Thanks!
Crash Signature: [@ WrappedNativeProtoMarker ] [@ nsXPConnect::Traverse ] → [@ WrappedNativeProtoMarker ] [@ nsXPConnect::Traverse ]
Mozilla/5.0 (X11; Linux i686; rv:8.0a1) Gecko/20110707 Firefox/8.0a1 Setting status to Resolved Incomplete. Please reopen when you can provide more information.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
Blocks: 500103
You need to log in before you can comment on or make changes to this bug.