crash in rf-firefox-plugin@0x78cb4 with Roboform 1-05-002

RESOLVED FIXED

Status

()

Firefox
Extension Compatibility
--
critical
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: Scoobidiver (away), Unassigned)

Tracking

({crash, qawanted, steps-wanted})

19 Branch
x86_64
Mac OS X
crash, qawanted, steps-wanted
Points:
---

Firefox Tracking Flags

(firefox19- affected)

Details

(crash signature)

(Reporter)

Description

5 years ago
It's currently #9 top browser crasher in the first days of 19.0 on Mac OS X.

Signature 	objc_msgSend | rf-firefox-plugin@0x78cb4 More Reports Search
UUID	43a2c239-271b-4215-adbd-f26b72130221
Date Processed	2013-02-21 22:04:24
Uptime	18322
Last Crash	1.2 days before submission
Install Age	5.1 hours since version was first installed.
Install Time	2013-02-21 16:53:11
Product	Firefox
Version	19.0
Build ID	20130215130331
Release Channel	release
OS	Mac OS X
OS Version	10.8.2 12C60
Build Architecture	amd64
Build Architecture Info	family 6 model 42 stepping 7
Crash Reason	EXC_BAD_ACCESS / 0x0000000d
Crash Address	0x0
App Notes 	
AdapterVendorID: 0x8086, AdapterDeviceID: 0x 126GL Context? GL Context+ GL Layers? GL Layers+ 
Processor Notes 	sp-processor02.phx1.mozilla.com_25943:2008; exploitablity tool: ERROR: unable to analyze dump
EMCheckCompatibility	True
Adapter Vendor ID	0x8086
Adapter Device ID	0x 126

Frame 	Module 	Signature 	Source
0 	libobjc.A.dylib 	objc_msgSend 	
1 	rf-firefox-plugin 	rf-firefox-plugin@0x78cb4 	
2 	rf-firefox-plugin 	rf-firefox-plugin@0x18074a 	
3 	HIToolbox 	GetWindowProperty 	
4 	rf-firefox-plugin 	rf-firefox-plugin@0x1d7cb2 	
5 	Foundation 	__NSFireTimer 	
6 	CoreFoundation 	__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ 	
7 	CoreFoundation 	__CFRunLoopDoTimer 	
8 	CoreFoundation 	__CFRunLoopRun 	
9 	CoreFoundation 	CFRunLoopRunSpecific 	
10 	HIToolbox 	RunCurrentEventLoopInMode 	
11 	HIToolbox 	ReceiveNextEventCommon 	
12 	HIToolbox 	BlockUntilNextEventMatchingListInMode 	
13 	AppKit 	_DPSNextEvent 	
14 	AppKit 	-[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] 	
15 	XUL 	-[GeckoNSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] 	widget/cocoa/nsAppShell.mm:164
16 	AppKit 	-[NSApplication run] 	
17 	XUL 	nsAppShell::Run 	widget/cocoa/nsAppShell.mm:741
18 	XUL 	nsAppStartup::Run 	toolkit/components/startup/nsAppStartup.cpp:290
19 	XUL 	XREMain::XRE_mainRun 	toolkit/xre/nsAppRunner.cpp:3823
20 	XUL 	XREMain::XRE_main 	toolkit/xre/nsAppRunner.cpp:3890
21 	XUL 	XRE_main 	toolkit/xre/nsAppRunner.cpp:4084
22 	firefox 	main 	browser/app/nsBrowserApp.cpp:174
23 	firefox 	start 	

More reports at:
https://crash-stats.mozilla.com/report/list?signature=objc_msgSend+|+rf-firefox-plugin%400x78cb4

Comment 1

5 years ago
so what version of RoboForm it is?

and is it even RoboForm?

can be some other app using RoboForm DLL
(Reporter)

Comment 2

5 years ago
We don't have library versions on Mac, only debug identifiers.
rf-firefox-plugin 		FC7E70855E99388F9FE88549EBC939CB0

Version 1-05-002 is for the rf-firefox-addon@siber.com extension.

Comment 3

5 years ago
i will ask programmers.

we will try to determine version number nby signature.

Comment 4

5 years ago
(In reply to Vadim Maslov from comment #3)
> i will ask programmers.
> 
> we will try to determine version number nby signature.

Thanks Vadim, we'll also try to reproduce on our side once our QA team has the necessary cycles.
tracking-firefox19: ? → +
Keywords: qawanted, steps-wanted
(Reporter)

Comment 5

5 years ago
It's #15 top browser crasher in 19.0 on Mac OS X. With the new rules in https://wiki.mozilla.org/CrashKill/Topcrash, that doesn't qualify it for the topcrash keyword.
tracking-firefox19: + → ?
Keywords: topcrash

Updated

5 years ago
tracking-firefox19: ? → -

Comment 6

5 years ago
New rel RF 1.5.5 probably fixes it.

We could never reproduce it,
but we fixed a bug that seems to be related to this one.
This crash spiked on 2/17 and again on 3/7. Other than that it's been single digit crashes reported on other days.
there are only a handful of crashes in the last few days and all of them are with RF Version 1-05-002.  I think it is safe to say RF 1.5.5 fixed this.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.