Closed Bug 610709 Opened 15 years ago Closed 15 years ago

spike in crashes [@ PR_AtomicDecrement ] causes by java plugin [@ npjp2.dll@0x23d9 ]

Categories

(Core Graveyard :: Plug-ins, defect)

x86
Windows 7
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: scoobidiver, Unassigned)

References

Details

(Keywords: crash, regression)

Crash Data

Build: Mozilla/5.0 (Windows NT 6.1; rv:2.0b8pre) Gecko/20101108 Firefox/4.0b8pre From this build, there is a spike in crashes. They are all due to java plugin. Various versions of java are implied from 1.6.18 to 1.6.22. It is #8 top crasher in this build. Signature PR_AtomicDecrement UUID ce9183d4-625a-4028-9312-fc07a2101109 Time 2010-11-09 04:42:51.478819 Uptime 3219 Install Age 119322 seconds (1.4 days) since version was first installed. Product Firefox Version 4.0b8pre Build ID 20101108043306 Branch 2.0 OS Windows NT OS Version 6.1.7600 CPU x86 CPU Info GenuineIntel family 6 model 30 stepping 5 Crash Reason EXCEPTION_ACCESS_VIOLATION_WRITE Crash Address 0x7a4cf64f App Notes AdapterVendorID: 10de, AdapterDeviceID: 0641 Frame Module Signature [Expand] Source 0 nspr4.dll PR_AtomicDecrement nsprpub/pr/src/misc/pratom.c:312 1 xul.dll mozilla::plugins::parent::_releaseobject modules/plugin/base/src/nsNPAPIPlugin.cpp:1534 2 npjp2.dll npjp2.dll@0x23d9 3 xul.dll DoStopPlugin layout/generic/nsObjectFrame.cpp:2456 4 xul.dll nsStopPluginRunnable::Run layout/generic/nsObjectFrame.cpp:2505 5 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:609 6 xul.dll mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:110 7 xul.dll xul.dll@0xb0a9fb 8 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:202 9 xul.dll _SEH_epilog4 10 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:176 11 xul.dll nsBaseAppShell::Run widget/src/xpwidgets/nsBaseAppShell.cpp:181 12 xul.dll xul.dll@0xb0a9fb 13 xul.dll nsAppShell::Run widget/src/windows/nsAppShell.cpp:243 The regression range for the spike is: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=8cbe83542596&tochange=a0826dcd6228 More reports at: http://crash-stats.mozilla.com/report/list?range_value=4&range_unit=weeks&signature=PR_AtomicDecrement&version=Firefox%3A4.0b8pre
blocking2.0: --- → ?
I just had a quick look and the crashes seemed pretty spread out, some were plugin crashes, others were unrelated crashes. I filed bug 616387 on making crashes that happen in PR_Atomic(In,De)crement easier to separate out from each other. Is there any evidence that this spike is still going, or was this due to a problem on a specific site or a specific nightly build?
> Is there any evidence that this spike is still going, or was this due to a > problem on a specific site or a specific nightly build? Go to Graph tab in the report list of comment 0 to see the crash count evolution by buildday. It was a temporarily spike that last about 2 weeks and ended in 4.0b8pre/20101116 build.
http://tinyurl.com/3yxwdvr indicates there were 69 crashes on the trunk in the last week.
This is too generic to be helpful. PR_AtomicDecrement is being added to the skiplist, and we'll get better signatures then which might be actionable.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
blocking2.0: ? → ---
Depends on: 616387
Crash Signature: [@ PR_AtomicDecrement ] [@ npjp2.dll@0x23d9 ]
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.