-
Notifications
You must be signed in to change notification settings - Fork 1.9k
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changing displays causes intermittent hangs (crashes) #3726
Comments
Do you have your surface display active in addition to your external
display? Or is just the external display active when plugged into the
docking station?
čt 27. 2. 2020 v 7:41 odesílatel Pun-e <notifications@github.com> napsal:
… Version
2.2 A4
Operating system type + version
Win 10 64 Pro - Surface Pro
Behavior
I start the slicer, and everything is fine.
If I unplug my docking hub, sometimes (it used to be everytime, but it has
improved recently), I'm presented with this:
[image: image]
<https://user-images.githubusercontent.com/47851787/75418316-4a495b80-5987-11ea-8e95-e768cd048067.png>
This is PrusaSlicer scaled to my Surface's screen, failing to update to
the new resolution of my external monitor.
I'm not sure what information you need from me to properly diagnose this
issue, but just let me know. It's a very circumstantial bug but it always
pops up when I'm least expecting it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3726?email_source=notifications&email_token=ABMPSI63VNUCI453MPIRYDTRE5OADA5CNFSM4K4UYQMKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IQV3IIA>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMPSIYBAJK3JGCTCV5BCWLRE5OADANCNFSM4K4UYQMA>
.
|
Undocked = Surface in-built screen I saw this bug, but the person who opened it just abandoned it. I'm thinking they're probably associated |
Thanks, we have a windows laptop with a docking station with 2 display
outputs available, we can test it.
What is the model of your Surface? Is it a tablet style computer or a
laptop?
čt 27. 2. 2020 v 10:31 odesílatel Pun-e <notifications@github.com> napsal:
… Undocked = Surface in-built screen
Docked = 2 external HDMI monitors
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3726?email_source=notifications&email_token=ABMPSI6CUA4JCVMF4LDUIIDRE6B7JA5CNFSM4K4UYQMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENDT4VY#issuecomment-591871575>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMPSIZSOJDGYRRQQJ5ZNI3RE6B7JANCNFSM4K4UYQMA>
.
|
This model i7 + iris 540 graphics The next time it happens, is there any log or something I can get that will offer some further details / insights? |
We were able to reproduce the issue on one setup of one of our IT guys. We
were not able to reproduce the issue on our development laptop. It will
take some time to resolve the issue as we cannot reproduce on our
development computers.
čt 27. 2. 2020 v 14:23 odesílatel Pun-e <notifications@github.com> napsal:
… This model <https://en.wikipedia.org/wiki/Surface_Pro_4> i7 + iris 540
graphics
[image: image]
<https://user-images.githubusercontent.com/47851787/75449003-59003480-59c0-11ea-980d-28ae82c767ba.png>
The next time it happens, is there any log or something I can get that
will offer some further details / insights?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#3726?email_source=notifications&email_token=ABMPSI7GKVUGOJQATFSYOALRE65FPA5CNFSM4K4UYQMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENELPBY#issuecomment-591968135>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMPSI6HX76KBMDDWDJARMLRE65FPANCNFSM4K4UYQMA>
.
|
It happened when our IT guy put his computer to sleep after running slicer
on his laptop in standalone mode, and then he plugged his computer into his
docking station and then he woke up the computer by the power on button on
his docking station. Is this your scenario as well?
čt 27. 2. 2020 v 15:04 odesílatel Vojtech Bubnik <vojtech.bubnik@prusa3d.cz>
napsal:
… We were able to reproduce the issue on one setup of one of our IT guys. We
were not able to reproduce the issue on our development laptop. It will
take some time to resolve the issue as we cannot reproduce on our
development computers.
čt 27. 2. 2020 v 14:23 odesílatel Pun-e ***@***.***> napsal:
> This model <https://en.wikipedia.org/wiki/Surface_Pro_4> i7 + iris 540
> graphics
> [image: image]
> <https://user-images.githubusercontent.com/47851787/75449003-59003480-59c0-11ea-980d-28ae82c767ba.png>
>
> The next time it happens, is there any log or something I can get that
> will offer some further details / insights?
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#3726?email_source=notifications&email_token=ABMPSI7GKVUGOJQATFSYOALRE65FPA5CNFSM4K4UYQMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENELPBY#issuecomment-591968135>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABMPSI6HX76KBMDDWDJARMLRE65FPANCNFSM4K4UYQMA>
> .
>
|
I'm not too sure what "standalone mode" is, but yeah, going to sleep seems to make it more likely to happen. Although I can cause the issue to happen just by toggling power to my dock. When power is switched off, it counts as a disconnect. I literally just froze the slicer again testing that. It also seems more likely to happen after I slice something. Yeah, just tested that too. If I just open the program and don't slice anything it didn't freeze after 3 toggles, sliced a file and it froze on the next connection. Process:
For me, this will freeze it every time. Sometimes I can use slicer for a few seconds before it freezes but I've successfully frozen it 4 times in a row now |
We reproduced it on one laptop. When we tried to collect crash logs using https://docs.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps and to trigger the crash dump manually over the hanging process with https://docs.microsoft.com/en-us/sysinternals/downloads/procdump Create the process dump by executing the following command, or the one provided by a helper: ProcDump.exe -ma <process name or PID (Process ID)> we are no more able to reproduce the hang once we enabled crash dump collection for PrusaSlicer, so we are stuck. You may try to collect the crash dump for us if you manage. |
Version
2.2 A4
Operating system type + version
Win 10 64 Pro - Surface Pro
Behavior
I start the slicer, and everything is fine.
If I unplug my docking hub, sometimes (it used to be everytime, but it has improved recently), I'm presented with this:
This is PrusaSlicer scaled to my Surface's screen, failing to update to the new resolution of my external monitor.
I'm not sure what information you need from me to properly diagnose this issue, but just let me know. It's a very circumstantial bug but it always pops up when I'm least expecting it.
The text was updated successfully, but these errors were encountered: