Re: Issue 321294 in chromium: Crash with Matrox Power Desk software (TripleHead2Go and DualHead2Go devices)

[chro...@googlecode.com]

Comment #52 on issue 321294 by vang...@chromium.org: Crash with Matrox
Power Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

We need to get the Matrox unit inhouse to do some testing. Can anyone who's
having this issue point me to what device specifically they're using? Is it
one of these?

http://www.amazon.com/s/ref=nb_sb_noss_1?url=search-alias%3Daps&field-keywords=matrox+dualhead2go&rh=i%3Aaps%2Ck%3Amatrox+dualhead2go




--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Cc: eso-chr...@chromium.org vang...@chromium.org

Comment #53 on issue 321294 by vang...@chromium.org: Crash with Matrox

Power Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

Issue 349788 has been merged into this issue.

[chro...@googlecode.com]

Comment #54 on issue 321294 by jpotta...@gmail.com: Crash with Matrox Power

Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

I have the DualHead2Go Digital SE.
http://www.matrox.com/graphics/en/products/gxm/dh2go/digital_se/
This, along with the ME (Mac edition) are the two newest in the range and
come in Dual and Triple outputs. There are legacy analog ones they still
make I believe but I am fairly confident that the maximize software hook
causing the problem with Chrome is common to all the devices that use the
PowerDesk suite.

[chro...@googlecode.com]

Comment #55 on issue 321294 by hagronne...@gmail.com: Crash with Matrox

Power Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

I also have the DualHead2Go Digital SE and can confirm I have the issue.
http://www.matrox.com/graphics/en/products/gxm/dh2go/digital_se/

[chro...@googlecode.com]

Comment #56 on issue 321294 by marior...@gmail.com: Crash with Matrox Power

Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

I have the DualHead2Go Analog Edition and suffer from constant Chrome
crashes. It has been installed for about 3 years now.

[chro...@googlecode.com]

Comment #57 on issue 321294 by dfo.tt...@gmail.com: Crash with Matrox Power

Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

Matrox DualHead2Go Digital Edition, firmware ver 2.3.53
Matrox PowerDesk (desktop management software) version 1.17.2202.0614
2.08.02 GXM.

[chro...@googlecode.com]

Comment #58 on issue 321294 by dfo.tt...@gmail.com: Crash with Matrox Power

Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

Matrox TripleHead2Go Digital Edition, firmware ver 2.3.53

Matrox PowerDesk (desktop management software) version 1.17.2202.0614
2.08.02 GXM

[chro...@googlecode.com]

Comment #59 on issue 321294 by vange...@google.com: Crash with Matrox Power

Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

Thank you, folks. Order placed. We should be able to test in-house by early
next week.

[chro...@googlecode.com]

Comment #60 on issue 321294 by MarcZel...@gmail.com: Crash with Matrox

Power Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

I have the triple head to go analog, the original edition/release.

We do appreciate that the team can look into the issue.

[chro...@googlecode.com]

Comment #62 on issue 321294 by jpotta...@gmail.com: Crash with Matrox Power

Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

Bumped again. I cannot understand why when it seems so simple. It was
working fine pre 32 and the community has also very clearly mapped the
issue above. I guess we Dual/TripleHead2Go users and Chrome were not meant
to be.

[chro...@googlecode.com]

Comment #65 on issue 321294 by g...@groupworkflow.com: Crash with Matrox

Power Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

Here is a followup from Matrox Support (could be helpful in the short term
for people):

There's an issue related to the latest version of Google Chrome and it has
been brought to our attention.

We have no fix, but there's a workaround. As long as you don't maximize
your Chrome, you should be able to close it and reopen correctly.

Please follow the steps below and you should be able to start Chrome again:

1. Right click on the Desktop and click on "Launch Matrox Power Desk";

2. Click on "Desktop Management";

3. Uncheck the box that says "Maximize windows" and click on Apply;

4. Open Chrome and make sure it's not in Full Screen. You can
manually resize it to make it fit the display, just make sure that you
don't maximize it;

5. Go back into Power Desk and Check the "Maximize windows" box and
click on Apply.

If it's not in Full Screen, you should be able to close and reopen it no
problem.

We're working on the issue to have a definite solution as soon as possible.

[chro...@googlecode.com]

Comment #66 on issue 321294 by g...@groupworkflow.com: Crash with Matrox

Power Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

Here is another way to get Chrome working. Restart your computer and then
login to windows. As soon as you have the ability to click on the Google
Chrome browser icon, then do it (2 or 3 times if necessary). Chrome should
open no matter what. Then you can follow post #65 in the meantime. This
works for me. Hope you find it helpful until this issue is stabilized and
fixed for good. :)

[chro...@googlecode.com]

Comment #67 on issue 321294 by g...@groupworkflow.com: Crash with Matrox

Power Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

. . . #66 probably works because you are opening Chrome before the Matrox
software is fully initialized during Windows startup...just guessing (but
it works every time for me). . .

[chro...@googlecode.com]

Comment #68 on issue 321294 by jpotta...@gmail.com: Crash with Matrox Power

Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

With the recent bump of this issue to 36 I have actually been forced onto
another browser for now. Had not tried Opera for years but it is actually
really great these days. Chromium based, super fast and works fine with
Matrox.

[chro...@googlecode.com]

Comment #71 on issue 321294 by scott.ca...@gmail.com: Crash with Matrox

Power Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

I get that this is not a priority because you feel its not your issue (even
though you created the issue in the first place) but this is getting
ridiculous. I made the switch to chrome and then a few months later I am
met with this. I have stuck with your browser for quite a while, despite
this issue, but I'm on my last leg. Instead of fixing an issue many people
are having it keeps getting pushed lower and lower while you pawn off
ownership of a bug you introduced on another vendor. If you break it fix
it. Don't expect someone else to clean up a mess your company made.

[chro...@googlecode.com]

Updates:
Owner: jba...@chromium.org

Comment #72 on issue 321294 by jba...@chromium.org: Crash with Matrox

Power Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

(No comment was entered for this change.)

[chro...@googlecode.com]

Updates:
Status: Started

Comment #73 on issue 321294 by vang...@chromium.org: Crash with Matrox

[chro...@googlecode.com]

Comment #74 on issue 321294 by lachance...@gmail.com: Crash with Matrox

Power Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

you can add my name to the list of those wanting a solution.
I have found that if I hold my control key and launch Chrome it will open
to encompass all three monitors. Then if I windows it and place it in the
monitor of my choice then maximize it it will work fine. If I try to open
it without holding the control key it will always crash with the Woah!
error. Like everyone else it's not a show stopper but it is annoying.

Thanks for you understanding and support.

Cliff

[chro...@googlecode.com]

Updates:
Cc: robertsh...@chromium.org b...@chromium.org s...@chromium.org

Comment #77 on issue 321294 by jba...@chromium.org: Crash with Matrox

Power Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

The simplest way I've found to cause a similar problem (no hardware needed)
is to do a "ShowWindow(hwnd(), SW_SHOWDEFAULT);" at the end of in
HWNDMessageHandler::OnCreate. This completely messes up the order in which
we do the initialization of the window and breaks everything. I can get rid
of the crash easily enough, but everything remains black.

Interestingly enough, the blackness (and no crash) also happens if I
do "window_style_ &= ~ WS_MAXIMIZE;" in gfx::WindowImpl::Init (when Chrome
starts maximized). With that, it seems that
a "ExecuteSystemMenuCommand(SC_MAXIMIZE);" also causes some weird
initialization order. So it seems that we've got very particular ordering
constraints when creating a window.

For now I'm thinking of just blacklisting the dll in the browser process.
It will prevent this fancy maximize feature from working, but at least it
will avoid crashes until we get a better solution.

[chro...@googlecode.com]

Comment #78 on issue 321294 by matte3...@gmail.com: Crash with Matrox Power

Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

I can only speak for myself of course, but I would prefer it if the crash
was left in if the alternative is to break PowerDesk functionality. The
maximize feature improves workflow immensely over having to manually resize
and position windows whenever you want to move them around.

I've been dealing with this crash for so long now that I've learned to work
around it. If I open Chrome immediately after my computer starts, it won't
crash, because PowerDesk has not started yet. Then it's just a matter of
not closing Chrome unless it has been un-maximized first.

[chro...@googlecode.com]

Comment #79 on issue 321294 by jpotta...@gmail.com: Crash with Matrox Power

Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

I tend to agree. Leo (Matrox rep references in this thread) emailed me
just today to say he was of the understanding that their dev team was
testing a fix/workaround at the moment. If this is indeed released soon
but Powerdesk is blacklisted who knows how long it will take for the ban to
get rescinded.

I feel your pain with the longevity of this crash. I am not so diligent
and all the workarounds in the world don't stop it from happening
completely - the worst is creating a new Chrome window with a maximised one
already open - makes the blood boil.

[chro...@googlecode.com]

Comment #80 on issue 321294 by Centauri...@gmail.com: Crash with Matrox

Power Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

As long as we're talking about possible workarounds, here is another idea:
If you can already detect the DLL during startup (you mentioned the ability
to blacklist it), then why not just force the window to start in a
non-maximized state when you detect that the DLL is loaded? I'm not saying
it's the best solution possible, but it's a workaround with simple logic,
and is better than the current situation for all cases.

[chro...@googlecode.com]

Comment #84 on issue 321294 by jpotta...@gmail.com: Crash with Matrox Power

Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

Spoke to soon. Now Chrome just appears to be blacklisted for the hooks in
Powerdesk and therefore does not maximize to a single display anymore,
arguably just as annoying as the previous bug. Works for other software.

Can anyone confirm?

[chro...@googlecode.com]

Comment #85 on issue 321294 by m.pet...@northdakotadevelopments.com: Crash

with Matrox Power Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

Has this been resolved now? Should I update the driver?

[chro...@googlecode.com]

Comment #87 on issue 321294 by jkm...@gmail.com: Crash with Matrox Power

Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

The driver package available for a TripleHead Analog still indicates it was
last updated in 2010. Can anyone confirm it has actually been updated?

[chro...@googlecode.com]

Comment #89 on issue 321294 by jpotta...@gmail.com: Crash with Matrox Power

Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

I am a DualPort2Go SE and just following the link above leads to a May 2014
package for Powerdesk (not the firmware one). My understanding is that
Powerdesk is common software to the whole range.

[chro...@googlecode.com]

Comment #90 on issue 321294 by g...@groupworkflow.com: Crash with Matrox

Power Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

Dear All,

Matrox has fixed this issue and released new drivers around May 22nd 2014
FYI to address it: Yes, the update has been released today.
You can find it at:
http://www.matrox.com/graphics/en/support/drivers/download/latest/

or go to their driver update wizard and select your OS and product etc and
it will take you directly to a updated version of the driver/software to
fix the issue.

Otherwise, here is a workaround that also worked for me prior to them
having a update:

There is a workaround and it is as follows:
1. Open "Matrox PowerDesk" and select "Desktop Management"

2. Under the "Window management" heading, uncheck the "Maximize
windows" setting then click on "Apply" at the bottom

3. Do not close PowerDesk just yet.

4. You should now be able to open Google Chrome and resize it to fit
on screen..

5. Back in PowerDesk, place the check mark back in the "Maximize
windows" check box. And click on "Apply"

6. Google Chrome should now behave as normal however make sure it is
not in the "maximized" state when it is closed.

and . . .

As long as you remember to minimize before closing, you can maximize it no
problem DURING your session...otherwise, if you get caught with the Whoa
crash again just repeat the numbered steps above (be sure to minimize prior
to closing chrome).

And once we have the final fix, we'll publish it on our website...however,
they published the FIX above so these workaround steps should not be needed
if you update your drivers/software.

In case it happens again you will know what to do though with this post as
well.

Please let me know if it works for you. It did it for me (at least for
now)...smile.

[chro...@googlecode.com]

Comment #93 on issue 321294 by toolsky...@gmail.com: Crash with Matrox

Power Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

fix works for Chrome but does not for Opera ...

[chro...@googlecode.com]

Comment #94 on issue 321294 by eric.arm...@personalliberty.com: Crash with

Matrox Power Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

@rmbarn...@gmail.com
I'm not sure if you would like to attempt the Matrox driver, but I can tell
you that I was able to load the software for the analog version of the
DualHead2Go device I have, and it appears to be working just fine. I have
been using it since May, 23rd, 2014. I posted under #88 in this thread.

[chro...@googlecode.com]

Comment #95 on issue 321294 by rmbarn...@gmail.com: Crash with Matrox Power

Desk software (TripleHead2Go and DualHead2Go devices)
http://code.google.com/p/chromium/issues/detail?id=321294

@eric.arm...@personalliberty.com

I tried your workaround when first proposed. Doesn't seem to work for the
TrippleHead variant in that I have many non-Chrome related problems using
that version of the software w/ Analog.

[chro...@googlecode.com]

Comment #96 on issue 321294 by buchalja...@gmail.com: Crash with Matrox

Power Desk software (TripleHead2Go and DualHead2Go devices)

https://code.google.com/p/chromium/issues/detail?id=321294

Very frustrating. Fixed this years ago with some workaround. Office
burglarized. Rebuilding system. Can't remember what I did, now I can't
run Chrome. Pathetic performance by Matrox and Google.

[chro...@googlecode.com]

Comment #97 on issue 321294 by smok...@chromium.org: Crash with Matrox

Power Desk software (TripleHead2Go and DualHead2Go devices)
https://code.google.com/p/chromium/issues/detail?id=321294

Issue 433844 has been merged into this issue.

[chro...@googlecode.com]

Comment #99 on issue 321294 by a...@chromium.org: Crash with Matrox Power

Desk software (TripleHead2Go and DualHead2Go devices)
https://code.google.com/p/chromium/issues/detail?id=321294

Issue 451067 has been merged into this issue.

[chro...@googlecode.com]

Comment #101 on issue 321294 by sdem...@chromium.org: Crash with Matrox

Power Desk software (TripleHead2Go and DualHead2Go devices)
https://code.google.com/p/chromium/issues/detail?id=321294

Per #100, I will share the workaround in #25

[chro...@googlecode.com]

Comment #103 on issue 321294 by jba...@chromium.org: Crash with Matrox

Power Desk software (TripleHead2Go and DualHead2Go devices)
https://code.google.com/p/chromium/issues/detail?id=321294

Issue 431581 has been merged into this issue.