You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From past two weeks to in windows 10 or 11 facing the issues of browser shut down while launch weasis to open the images, We temporarily solved by installing lowest version like 3.8. some time it opening in fire fox but very next day it is getting closed for fire fox also. it is being major and user cant use weasis, so far 4 users from different location stopped using since lower version they feel not happy work. looking for your support under higher priority
What version of Weasis are you running?
4.5,4.2
On which system the problem occurs?
Windows
Relevant log output
No response
Additional contextual elements
No response
The text was updated successfully, but these errors were encountered:
arunjoshtech
changed the title
Browser getting shut down while launch Weasis for Chrome ,edge and for
Browser getting shut down while launch Weasis for Chrome ,edge and fire fox
Aug 31, 2024
No problems similar to your description have been observed in the various Weasis integrations on Windows 10 and 11. Moreover, there's no direct link between the browser and Weasis.
As already said, without a procedure to reproduce the problem or explicit error logs, we won't be invistigating it any further.
Describe the bug. What happened?
From past two weeks to in windows 10 or 11 facing the issues of browser shut down while launch weasis to open the images, We temporarily solved by installing lowest version like 3.8. some time it opening in fire fox but very next day it is getting closed for fire fox also. it is being major and user cant use weasis, so far 4 users from different location stopped using since lower version they feel not happy work. looking for your support under higher priority
What version of Weasis are you running?
4.5,4.2
On which system the problem occurs?
Windows
Relevant log output
No response
Additional contextual elements
No response
The text was updated successfully, but these errors were encountered: