Crash in [@ xmutil.dll]
Categories
(Core :: General, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox68 | --- | affected |
People
(Reporter: lizzard, Unassigned)
Details
(Keywords: crash)
Crash Data
This bug is for crash report bp-fb02be23-ab59-462a-8baa-306ad0190416.
In the nightly builds from 4-15, a lot of crashes are showing up for the first time, with signatures containing xmutil.dll. This seems to be something to do with maps and MapInfo Pro. Not sure if it may be their bug or a change in Firefox.
Top 4 frames of crashing thread:
0 xmutil.dll xmutil.dll@0x5b57e
1 xmutil.dll xmutil.dll@0xa6d31
2 xmutil.dll xmutil.dll@0xcfa6f
3 xmutil.dll xmutil.dll@0x664ff
Comment 1•6 years ago
|
||
Is there anything we can do with these crashes, Eric?
Comment 2•6 years ago
|
||
Looks as if all three of these crashes were happening in 20190418224226, but I haven't seen any crashes on 68 since then.
Comment 3•6 years ago
|
||
(In reply to Andrew Overholt [:overholt] from comment #1)
Is there anything we can do with these crashes, Eric?
Sounds like we should hold off and see if this has resolved itself.
Comment 4•6 years ago
|
||
The priority flag is not set for this bug.
:sphilp, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 5•6 years ago
|
||
Seems like the crashes have returned, if you can take a look Eric
Comment 6•6 years ago
|
||
(In reply to Stuart Philp :sphilp from comment #5)
Seems like the crashes have returned, if you can take a look Eric
I think the bot just wanted a priority. I'm not seeing any crashes from this beyond the 20190418224226 nightly build.
Updated•6 years ago
|
Comment 7•6 years ago
|
||
The priority flag is not set for this bug.
:sphilp, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 8•6 years ago
|
||
P3 for now. Leaving open in case the crashes return, but for now I am not seeing anything recently.
Comment 9•6 years ago
|
||
All three of these signatures are no longer showing up. I am going to resolve this as WFM for now. We can reopen if the signatures resurface.
Description
•