Closed Bug 669431 Opened 15 years ago Closed 15 years ago

Firefox 7.0a1 Crash Report [@ nvumdshimx.dll@0x384c8 ]

Categories

(Core :: Graphics, defect)

Product:
Core
Component:
Graphics
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: hAbI_rAbI, Unassigned)

Details

Crash Data

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:7.0a1) Gecko/20110703 Firefox/7.0a1 Build ID: 20110703030232 Steps to reproduce: Clicked on Tab and browser crashed. Looks like it's related to the nVidia drivers. I'm currently using version 275.33 for Notebooks. The only newer version is 275.50 Beta.
OS: Other → Windows 7
Hardware: All → x86_64
Crash Signature: [@ nvumdshimx.dll@0x384c8 ]
i would say : Report it to nvidia
Component: General → Graphics
Product: Firefox → Core
QA Contact: general → thebes
I've reported it to nvidia too now. I don't know if it's the driver's fault or the browser's though.
Component: Graphics → General
Product: Core → Firefox
Component: General → Graphics
Product: Firefox → Core
The guys at nVidia said they couldn't reproduce the issue and said it was Firefox specific. If they can reproduce it they will try to fix it but till then I think they consider this to be something that has to be fixed on the Firefox side.
The crash happens in nvumdshimx.dll and that is not a part of Firefox. How should we fix a bug inside that dll ?
Oh well I filed a bug report there. I'll just let this pan out. If not I'll just have to live with rare random crashes O_O. Either way such crashes didn't happen in the past so wouldn't that suggest that a change in Firefox made this issue appear? Maybe if there was a way to pinpoint the change on this side it would shed light on what the problem is on the driver side. Just a thought.
(In reply to comment #6) > Oh well I filed a bug report there. I'll just let this pan out. If not I'll > just have to live with rare random crashes O_O. Setting this then as resolved, since it doesn't seem as a Fx issue. But if you still see this issue after a fix from NVidia, feel free to reopen this bug. Thanks
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.