1893413 - The Italian dictionary when you compose an email and select menu-->insert-->image freeze TB.

Status: RESOLVED WORKSFORME

(Thunderbird :: Message Compose Window, defect)

Description

[[:Aureliano Buendía]]

With the Italian dictionary installed, composing an email and selecting menu-->insert-->image freezeTB. I need to end the task with windows tasks manager.
In safe mode I have no issues.

Comment 1

[Vlad Lucaci, Thunderbird QA (:vlucaci)]

Hello,

I have tried to reproduce this issue using 126.0b1(20240423160232) , 115.10.1(20240417192958) and 124.0(20240312201328) with Windows 11 and Windows 10 using the information and steps from the Description but did not manage to encounter it.

Could you maybe send me an email with your troubleshooting information (Menu -> Help -> Troubleshooting information ->Send via Email) to make sure that no other settings or configurations are causing this issue instead.

Comment 2

[Rob Lemley [:rjl]]

I'm not able to reproduce either.

Comment 3

[[:Aureliano Buendía]]

(In reply to Vlad Lucaci, Desktop QA (:vlucaci) from comment #1)

Could you maybe send me an email with your troubleshooting information (Menu -> Help -> Troubleshooting information ->Send via Email) to make sure that no other settings or configurations are causing this issue instead.

sent email with required information now

Comment 4

[[:Aureliano Buendía]]

Could be usefull the profiler result https://share.firefox.dev/4bandaH ?

Comment 5

[[:Aureliano Buendía]]

I suspect that the problem is related to the fact that I use 3 screens at work and maybe the third TB window (insert-image) remains assigned to one of the screens that are now disconnected...

Comment 6

[Vlad Lucaci, Thunderbird QA (:vlucaci)]

Hello,

I tried to reproduce this again using 126.0b1(20240423160232) , 115.10.1(20240417192958) and 124.0(20240312201328) with Windows 11 and Windows 10 with a 2 and 3 monitor hardware configuration (via Dell D6000 hub) and was unable to reproduce it again.

If this issue is still reproducible for you, could you please help us with a regression range using the Mozregression GUI tool?

I will provide some steps to make it easier for you:

You have to determine a build that reproduces the issue. In your case it seems the latest Thunderbird v126.0b1 (64-bit), right? You can retest it anytime.

Then you should find one that does NOT reproduce it. Detailed steps:
a. Open Mozregression app;
b. Click "File" -> "Run a single build";
c. On the "Single Run Wizard" pop-up, "Basic configuration", select "Thunderbird" and click "Next".
d. On the "Profile selection" page, just click the "Next" button.
e. On the "Build selection" select a date (dates before 2024-04-24 you find one that does not reproduce the issue) on the from the drop-down on the left and click "Finish".
f. Now the mozregression app will open a thunderbird build of the selected date and you can use it, close it and open another. (make a note of the version that does not reproduce the issue)

You will use mozregression app to "bisect" builds that reproduce the issue by builds that do not reproduce it in search of the one build/changeset that introduced the issue, in the first place:
a. Open mozregression-gui.exe
b. Click "File" -> "Run a new bisection"
c. On "Basic configuration" screen, select "Thunderbird" and click "Next" button.
d. Skip "Profile selection" screen by the "Next" button.
e. On the Bisection wizard screen, you will need to select a build that reproduces the issue and one that does not:
e1. In the "Last known good build:" section, select "date" on the right drop-down and the date of the build you found NOT to reproduce the issue.
e2. In the "First known bad build:" section, select "date" on the right drop-down and the date of the build you found to reproduce the issue.
f. Click "Finish" to start the bisection process.
g. Builds will open one-by-one, you will need to test each one of them and see whether the issue reproduces. If it reproduces, then you need to select the "bad" button in the mozregression window and if not, you need to select the "good" button.
h. When bisection is done, you will have the information in the "Log View" section of the mozregression window; bisection may also fail due to not enough builds, but the logs can always be useful.
Copy the logs in a text file and attach it to this bug.

If there is still information you need regarding the regression process, please request information from me.
Thank you for your contribution!

Comment 7

[[:Aureliano Buendía]]

Hi and thanks for tips about Mozregression.
It was my mistake: After resetting the dock that connects my 3 screens, the problem never recurred.
Sorry for wasting your time.