eM Client V8.2 Beta

The new Emojis in V8.2 Beta are definitely way better as not only is there way more of them, but they now are (in proportion) to the typed text and not too big / tall :grinning: :ok_hand:

Ps The only issue my bro and i had was that we had to delete our old databases and re-setup our IMAP accounts as the Beta (closed within a few secs) after upgrading, but those sort of things sometimes happen in Beta testing as expected.

4 Likes

Everything’s working like a charm for me. The integration of the videoconferencing tools is really great.

4 Likes

No problem here with IMAP. I hesitated a bit to install the beta because the release notes mention a database update, but my 8.2 beta (now beta 2, version 8.2.1107) works like a charm as well.

2 Likes

This has been there in the 8.2 beta for a while.

If you’re like me, I am zooming around the application like crazy as soon as it has started looking for any changes and new features. It crashed every time when doing that on first start after an upgrade.

But if you update, then after eM Client has restarted, just leave it alone for a few minutes before you do anything, then in most instances it seems OK.

Shouldn’t be like that but I am wondering if there is some additional database conversion going on that was interrupted and causes the shutdown. Of course if you start fresh with a new database as you finally did, that bypasses that issue. I mentioned this in another post that when testing, it is advisable to try both ways. :slightly_smiling_face:

As with most betas, there are issues. If you experience anything that does not cause the error submission pop-up, you can send your observations to testing@emclient.com. During an open beta they rely on you communicating with them so that these things can be fixed before the official release.

1 Like

Yes @Gary i am also thinking the same that the Beta 8.2 is possibly doing some sort of database conversion in the background after upgrading. Either that or its just bugged. Anyway i emailed the testing email address as it happened on two different Win 10 pcs both with Gmail and other IMAP accounts. Its been working perfectly since we re-setup the accounts now upgraded to V8.2.1107

1 Like

are there any restrictions about running eM Client in a vm? any experiences?

looks like most have the beta version installed on their live environment, with funny moments :smiley:

Should run fine in a VM like Oracle Virtual Box

Ps Just click check for update in the menu after you install the Beta to get the latest build which then seems way more stable.

1 Like

Yes, it runs fine. I used Virtual Box regularly for testing eM Client.

2 Likes

Does anyone have a link for MacOS V8.2 Beta?

This is not something we would expect happening even with the beta. And we are really concerned about this one. So you didn’t get our standard error dialog (asking to send the report to us) and the application terminated immediately after the update? If it is the case, can you send as an error report from Windows Event Viewer? That would help us a lot to diagnose it.
Otherwise we are pretty confident about the stability of that beta, so this is something we would really like to target as soon as possible.

Gary, this is weird. Can you take a look in the Windows Event Viewer, if the crash can be found there?

I submitted all the error dialogue popups under my registered email address.

I will have some time on Wednesday 17 March to do some testing, and will recreate it then, and send you any additional info.

Yes when the V8.2.x Beta closes shortly after opening (after the update from V8.1.1060.0 / V8.1.1087), you don’t get an error box to even send the error report. You just arrive back at the desktop.

All you can do then is keep opening EMC until it stays open, and then is ok again for a while. This never was an issue with V8.1.x Betas and is happening on both my and my bros Win 10 pc’s build 20H2 (19042.867).

Even with the latest Beta V8.2.1107 after deleting the database completely and re-adding my two IMAP accounts, it will randomly close within a few seconds of opening and (no error box to send the reason).

Ps I don’t know where in the “Event Viewer” it shows the actual error to send when there is no dialogue box ? I can do some testing on upgrading from V8.1.1060.0 / V8.1.1087 again if someone can advise me where to see the error in Event Log.

Hello, event viewer is here to diagnose such situations.

This error (crash) should be visible under Application section and we are very curious what is inside.

1 Like

After upgrading to 8.2 beta with free license support, the app crashes when i want to edit my accounts. cant find any error in log.

@Michal_Burger Thanks for the Event Viewer info. I will go back to V8.1 latest builds and restore my old EMC backups and try upgrading again to see if i can replicate the problems & see errors in Event Viewer.

1 Like

@Michal_Burger Ok My Bro and i have just had eM Client Beta V 8.2.1107 randomly close within a few seconds of opening (with no crash report box) as above mentioned from Upgrading or even when Not upgrading with the new Beta and the below is what is shown in the Event Viewer error report on both Win 10 20H2 computers. I’ve emailed the EMC testing email address with the below error.

Security-SPP

Offline downlevel migration succeeded.

BODY{font:x-small ‘Verdana’;margin-right:1.5em} .c{cursor:hand} .b{color:red;font-family:‘Courier New’;font-weight:bold;text-decoration:none} .e{margin-left:1em;text-indent:-1em;margin-right:1em} .k{margin-left:1em;text-indent:-1em;margin-right:1em} .t{color:#990000} .xt{color:#990099} .ns{color:red} .dt{color:green} .m{color:blue} .tx{font-weight:bold} .db{text-indent:0px;margin-left:1em;margin-top:0px;margin-bottom:0px;padding-left:.3em;border-left:1px solid #CCCCCC;font:small Courier} .di{font:small Courier} .d{color:blue} .pi{color:blue} .cb{text-indent:0px;margin-left:1em;margin-top:0px;margin-bottom:0px;padding-left:.3em;font:small Courier;color:#888888} .ci{font:small Courier;color:#888888} PRE{margin:0px;display:inline}

-

-

16394

0

4

0

0

0x80000000000000

29589

Application

mikes

Windows Error Reporting

Fault bucket 2303857795176518903, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: MailClient.exe
P2: 8.2.1107.0
P3: 602c44b3
P4: coreclr.dll
P5: 5.0.421.11614
P6: 602c3bc7
P7: c0000005
P8: 001a668b
P9:
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA05C.tmp.mdmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA33C.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA35C.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA35A.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA37A.tmp.txt
\?\C:\Users\michael\AppData\Local\Temp\WERA3BC.tmp.appcompat.txt

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MailClient.exe_dddafd39deb4b5a1dbb8f6cd20f6fe60dcfdd_d7ccc0b4_7bfce8e3-678b-43e2-9623-d58d5a090940

Analysis symbol:
Rechecking for solution: 0
Report Id: 3d794888-9874-48fd-8ddf-6cea0d89bb2f
Report Status: 268435456
Hashed bucket: 573e669a249d52310ff8f2755682d4f7
Cab Guid: 0

BODY{font:x-small ‘Verdana’;margin-right:1.5em} .c{cursor:hand} .b{color:red;font-family:‘Courier New’;font-weight:bold;text-decoration:none} .e{margin-left:1em;text-indent:-1em;margin-right:1em} .k{margin-left:1em;text-indent:-1em;margin-right:1em} .t{color:#990000} .xt{color:#990099} .ns{color:red} .dt{color:green} .m{color:blue} .tx{font-weight:bold} .db{text-indent:0px;margin-left:1em;margin-top:0px;margin-bottom:0px;padding-left:.3em;border-left:1px solid #CCCCCC;font:small Courier} .di{font:small Courier} .d{color:blue} .pi{color:blue} .cb{text-indent:0px;margin-left:1em;margin-top:0px;margin-bottom:0px;padding-left:.3em;font:small Courier;color:#888888} .ci{font:small Courier;color:#888888} PRE{margin:0px;display:inline}

-

1001

0

4

0

0

0x80000000000000

29588

Application

mikes

-

2303857795176518903

1

APPCRASH

Not available

0

MailClient.exe

8.2.1107.0

602c44b3

coreclr.dll

5.0.421.11614

602c3bc7

c0000005

001a668b

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA05C.tmp.mdmp \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA33C.tmp.WERInternalMetadata.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA35C.tmp.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA35A.tmp.csv \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA37A.tmp.txt \?\C:\Users\michael\AppData\Local\Temp\WERA3BC.tmp.appcompat.txt

\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_MailClient.exe_dddafd39deb4b5a1dbb8f6cd20f6fe60dcfdd_d7ccc0b4_7bfce8e3-678b-43e2-9623-d58d5a090940

0

3d794888-9874-48fd-8ddf-6cea0d89bb2f

268435456

573e669a249d52310ff8f2755682d4f7

0

Event Viewer (Application error)

Faulting application name: MailClient.exe, version: 8.2.1107.0, time stamp: 0x602c44b3
Faulting module name: coreclr.dll, version: 5.0.421.11614, time stamp: 0x602c3bc7
Exception code: 0xc0000005
Fault offset: 0x001a668b
Faulting process id: 0x3b10
Faulting application start time: 0x01d719a0690b9354
Faulting application path: C:\Program Files (x86)\eM Client\MailClient.exe
Faulting module path: C:\Program Files (x86)\eM Client\coreclr.dll
Report Id: 3d794888-9874-48fd-8ddf-6cea0d89bb2f
Faulting package full name:
Faulting package-relative application ID:

  • 1000 0 2 100 0 0x80000000000000 29586 Application mikes
  • MailClient.exe 8.2.1107.0 602c44b3 coreclr.dll 5.0.421.11614 602c3bc7 c0000005 001a668b 3b10 01d719a0690b9354 C:\Program Files (x86)\eM Client\MailClient.exe C:\Program Files (x86)\eM Client\coreclr.dll 3d794888-9874-48fd-8ddf-6cea0d89bb2f

Event Viewer (.NET Runtime) error

Application: MailClient.exe
CoreCLR Version: 5.0.421.11614
.NET Version: 5.0.4
Description: The process was terminated due to an internal error in the .NET Runtime at IP 5072668B (50580000) with exit code c0000005.

  • 1023 0 2 0 0 0x80000000000000 29585 Application mikes
  • Application: MailClient.exe CoreCLR Version: 5.0.421.11614 .NET Version: 5.0.4 Description: The process was terminated due to an internal error in the .NET Runtime at IP 5072668B (50580000) with exit code c0000005.

Hello, which version it was? There was a temporary bug with opening Exchange account preferences that may caused this in 8.2.1100. I’d recommend updating to 8.2.1107.

1 Like

that was 8.2.1100 indeed. i temporarly went back to 8.1 and restored backup.
ill try 8.2. 1107 within a few days.

I and my bro have now gone back to V8.1.1087 on both our Win10 pc’s due to the instability of V8.2.1107 Beta. We will wait till a later Beta of V8.2 and test again.

1 Like