Access violation when deleting emssages with conversation from Desktop EPIM

[duarte.framos]

For the past two versions of EssentialPIM Pro Portable 11.7.1 under Windows 10, whenever I delete a message from my Gmail inbox that is part of a conversation I get this Access violation error.

I generally have View > Layout set to either Vertical View or Vertical View (in Groups).
I get a new message in my inbox that is part of a previous conversation thread. The other messages from the same thread have already been deleted to the bin folder and are no longer in my inbox. Upon receiving the new message they are seemingly "pulled" from the bin folder back into the inbox and they show up correctly as "child" sub messages of the newly received message in the thread.

Whenever I select just the the new mail message I received and delete it with the [Del] key, the error message pops up and the inbox becomes blank.

EPIM doesn't crash, it keeps functioning after this, I just have to force refresh the view by changing folders from the left pane and get back to the inbox again.
From then I can delete the other messages from the thread that have been "pulled" from the bin without issues, but deleting the most recent message always triggers the bellow warning.

Access violation at address 00000000. Read of address 00000000.

Code: Select all

------------------------------------------------------------------------------
Exception log with detailed tech info. Generated on 27/09/2023 19:25.
You may send it to the application vendor, helping him to understand what had happened.
 Application title: DPFR.epim - EssentialPIM Pro Portable
 Application file: O:\NGL\Apps\EssentialPIM\EssentialPIM.exe
 Application: EssentialPIM Pro Portable 11.7.1  25/09/2023
------------------------------------------------------------------------------
Exception class: EAccessViolation
Exception message: Access violation at address 00000000. Read of address 00000000.
Exception address: 00000000
------------------------------------------------------------------------------
Main thread ID = 10700
Exception thread ID = 10700
------------------------------------------------------------------------------
Object Logs:
19:24:22.112  SetViewMode OK
19:24:21.633  SetViewMode 5
19:17:29.882  DBOpen OK
19:17:28.967  SetViewMode OK
19:17:28.459  SetViewMode 1
19:17:28.200  DBOpen
------------------------------------------------------------------------------
Active Controls:
19:25:33.279  MainForm FormPan FormPan2 MailForm MessagesPan MsgListPnl MessagesVT
19:25:31.296  MainForm FormPan TBXToolbar2 TopPan Top2TB FindCB
19:24:50.124  MessageEditForm PageControl1 TextTS TWebBrowser
19:24:26.601  MainForm FormPan FormPan2 MailForm MessagesPan MsgListPnl MessagesVT
19:17:28.457  MainForm
------------------------------------------------------------------------------
Exception stack
Stack list, generated 27/09/2023 19:25
(0115375F) [0155475F]
(01153805) [01554805]
(00FFA72C) [013FB72C]
(00FFB072) [013FC072]
(01009510) [0140A510]
(000D3817) [004D4817]
(0042632E) [0082732E]
------------------------------------------------------------------------------
Memory: 65461; free 57618
Display: 5120x2160 pixels, 32 bpp, 120 PPI
------------------------------------------------------------------------------
Updates: 1
Last update: 26/09/2023

[admin]

Thanks for providing a detailed description of the issue and for sharing the video and error log file. Although we weren't able to reproduce the specific AV error message, we did identify and should fix a glitch where previously deleted emails were reappearing in the "conversations" (which shouldn't be happening). By resolving this issue, we believe that the situation that led to the initial error should no longer be possible.

[duarte.framos]

Indeed I was experiencing that issue as well. On previous versions messages would reappear in the inbox when I deleted an incomplete thread, that is I did not select all messages that belonged to the thread before deleting, despite some of them already being in the bin folder.

Looking forward to the fix, Thanks

[admin]

We would also appreciate it if you could temporarily disable conversations to check if the Access Violation error persists. If the error is still there, please disable grouping and check if the issue still occurs. Thank you!

[duarte.framos]

From my limited testing it doesn't seem to happen if conversations are disabled, which seems to be the original source of the problem.

I'll report back if I manage to trigger it with conversations disabled.

[admin]

The issue should be fixed in the following build:
https://www.essentialpim.com/download/t ... Pro117.exe
Please feel free to install and let us know. Thanks!