Crash on adding/Removing a monitor

[midhat]

My Palemoon 8.0-x64 crashes every time I plug in/out a monitor to my laptop. I am running windows 7 64-bit. The display settings have been set to Extend the displays, and the monitors use different aspect ratio. Main screen is 16:9 and the external monitor is 4:3.

[Moonchild]

Can you please supply some more information about your system? What kind of graphics hardware are you running on? Can you also give as much information as possible about the crash itself? When exactly does it happen? Is the browser using fullscreen mode when you add/remove the monitor? Does the crash tell you a library name and address? What technical info can you supply?

Potential workaround: go to options -> advanced -> tab "general" -> uncheck "Use hardware acceleration when available"
... since I have a feeling it may be graphics driver related. Pale moon itself doesn't care about aspect ratio of screens.

[midhat]

I have a Geforce GT 220M. The browser is not running in full screen when I change the number of monitors. Unchecking "Use Hardware Acceleration" doesn't fix this. I have sent you the files generated by windows error reporting in a PM.

Edit: Unchecking "Use Hardware Acceleration" does fix this. I did not restart palemoon in the last try

[Moonchild]

The dump file you sent me indeed points to a regular app crash (not graphics related).

EDIT: I managed to pull the memory dump apart further and it DOES still reference Direct3D10 which should not be used any more if you have disabled hardware acceleration. Please try to switch HW accel off, completely exit and restart Pale Moon, and then try again?

Unfortunately, the info in the dump doesn't point to a specific module beyond "somewhere in xul" in the graphics library (thebes) section.

To verify and pinpoint the problem:

1. Could you please verify if this also occurs on Pale Moon 32-bit?
2. Could you please verify if this also occurs on Mozilla Firefox 32-bit if (1) is true?
3. If it also occurs on Mozilla Firefox builds, could you please report the crash to Mozilla and give me the Crash-ID from the Mozilla crash reporter so I can have a closer look?

[midhat]

Yes. Infact it is fixed by unchecking the Hardware Acceleration checkbox, and restarting palemoon. I did not restart in the previous instance.

Did not crash on Palemoon 8 32-bit
Did not test on Firerfox 8 32-bit
Did not crash on 64-bit Nightly 11.0a1 (2011-12-01)

(*off to remove all those firey foxes)