Search Results matching tag 'crash'

IMAP crashes

jdudeck — Tue, 19 Feb 2013 23:00:32 GMT

I have discussed this on the Pmail mailing list, where Brian Fluet has duplicated the same problems that I am experiencing. I am logging this on this forum in the hopes that the Pegasus developers will note the seriousness of the situation and fix the bug.

The problem is as follows: When opening an IMAP folder that is "fairly large" (ie. usually hundreds of messages), Pmail will open a blank window, and not display any message headers. When you try to close the window, Pmail will hang, then crash after several tens of seconds. This occurs with v4.63, and has been doing this for quite a few previous versions. This occurs on Windows XP 32-bit and Windows 7 64-bit. I have not tried it on other versions of Windows. This happens both with Linux IMAP servers and with Windows Exchange. Whenever it happens, the Folder Info... for the folder shows either 0 or 128 bytes in the header cache,

What may be helpful in tracing down this problem is that I have found a consistent way to force Pmail to correctly open the offending folders. The steps are as follows: 1.Open the folder in Thunderbird. 2. Move all but 20 messages temporarily to another folder. 3. Close Thunderbird. 4. Open the folder in Pmail. It will open normally. 5. Verify that the header cache (Folder Info...) contains more than 128 bytes. Normally it will have about 3k bytes at this point. 6. Close Pmail. 7. Open the folder in Thunderbird. 8. Move the rest of the messages back into the folder. 9. Close Thunderbird. 10. Open the folder in Pmail. It now opens correctly!

However, after a time, if more messages are added to the folder, it will again no longer open correctly. If you look at Folder Info... there will be 128 bytes in the header cache.

Also, if, when an IMAP folder does open correctly, you clear the header cache, it will now no longer open correctly.

Please somebody make sure the developers log and fix this bug. It is extremely annoying to have to use Thunderbird to access my folders. I would have already abandoned Pmail because of this, if I didn't find it even more vexing to make the change. I have been using Pmail since DOS days in the early 90's. I would be most grateful if even a patch was released just to fix this bug.

Sincerely,

John Dudeck

PMail 4.63 crashes if there are too many messages in the INBOX (IMAP folder)

veijalainenj — Wed, 09 May 2012 12:44:39 GMT

HI,

I have been using Pmail since 1997 and I never had this kind of problem.

Our email server was changed in March to become MS Exchange and the infrastructure stopped supporting POP3 access. So I had to configure the mail client to only use IMAP4 protocol. Around the same time my organisation moved to Microsoft virus protection system that is installed on my laptop (running XP), as well. After having configured the server addresses and security options correctly, I could connect to the mail server and Pmail showed the folders that the server offers. This did not work out straight away, though, but the mailer complained first that it cannot access the server. After several attempts and running the program up and down I could access the folders, but I could not access the INBOX. After upgrading to v.4.63 from 4.x the software began to work. But now it has turned out that if the INBOX at the server has hundreds of messages, the mailer cannot show them in the new mail window or fetch them. Rather it crashes either silently or in some cases the XP issues a series of memory access violation messages. This happens when I try to open some other folders (like sent mail) on the server. Sometimes the mailer only shows the header, but no contents, if it managed to fetch all the headers. I cannot say an exact limit for this problem to happen. In some case the mailer is unable to fetch/show the mail headers from the INBOX, but if I open another folder and then go back the INBOX folder and ask the mailer to open it, it is able to do it and fill it wiht the message headers. In one communication log instance ( run with -Z 32 option) it had fetched 182 mail headers and it crashed wiht memory violation, but I have also logs where the mailer could fetch 350 messages in the INBOX without problems. What might be the reason for this behavior? Is this a memory management problem? It is annoying that I have to clean the mailbox with my smart phone mailer that does not have sophisticated facilities (but that works no matter how many messages I have in the INBOX).

Re: Added a New User- Exits When Minimized

philherz — Sat, 10 Mar 2012 02:45:02 GMT

Good point!

It probably never closed properly because it always closes when minimized for some strange reason.

I tried a regular exit and restarted it.

It still closes (crashes????) when minimized!!!

Thoughts?

bfluet:
Pegasus Mail updates its configuration files when it closes so it needs to close cleanly in order for all changes made during that session to stick. If the user was added and configured but Pegasus never closed cleanly then configuration settings would have been lost.

How to deal with crashes and hangs/freezes

idw — Sun, 23 Oct 2011 13:27:20 GMT

If you happen to encounter crashes with Pegasus Mail or situations where it doesn't continue to work anymore (hanging or freezing) it is recommended to take the following steps:

First of all ensure you're using the most recent version of Pegasus Mail since it might already fix your issue(s). Additionally it may help to check for the most recent versions of the built-in HTML renderers: IERenderer and BearHtml. To retrieve the installed versions of any of the above check the following locations: Pegasus Mail's version information is displayed at the bottom of its About screen accessible via its Help menu. IERenderer provides a similar About screen accessible via its toolbar button (usually the rigthmost one on top of Pegasus Mail's main window). BearHtml provides its version information only after disabling IERenderer on its button menu, loading an HTML message into reader or preview and pressing Shift + F1: It'll show up on Pegasus Mail's leftmost status bar section at the bottom of its main window.

If none of the updates helps please start a forum search next for your issue using any of the following URLs: Crashes, hangs or freezes. If you already have an idea of what might be causing your issue you may want to do a more specific search like this one or that one. If you can't find any helpful suggestions this way you may want to post a new support request including the information from Pegasus Mail's Help => About Pegasus Mail => Info screen.

It might also be helpful to provide more details to our beta-reports address about your special issue using the MiniDump extension. Please make sure to be using its most recent version as well, starting with version 2.5.7.0 it provides an update screen via Pegasus Mail's Tools => Extensions => MiniDump menu entry. You should allow its installer to create a Windows Start menu group for accessing its various command options and reading its ReadMe file specifying details about the way it works.

Thanks in advance ...

Crash on opening

maxwelldm — Tue, 16 Aug 2011 14:07:07 GMT

Sudden problem developed yesterday afternoon, with no apparent reason. Running PM 4.5, with both regular filtering and Spamhalter enabled, in Win-7. When I opened PM in the afternoon, I got only a partial screen paint, (only New Mail folder listed on left, most of screen below blank), with a message in bottom left saying "Applying mail filtering rules", at which point it freezes. Clicking on the Close button elicits a window headed Pegasus Mail for Windows, saying Pegasus Mail for Windows is not responding, with choice of closing or waiting for PM to respond. I tried reinstalling PM. No go. Deleted PM entirely and reinstalled from scratch; still crashes. Now what do I do? (I can't disable filtering because I can't get to the tools menu.)

Pegasus Crash

sirob — Tue, 31 May 2011 08:18:59 GMT

All of a sudden, Pegasus (under Win 7) crashes whenever I try to view any message that contains an attachment or image.

I have enclosed a screenshot of the resulting error message.

Pegasus Mail crashing on Windows 7 32bit

Greenman — Fri, 20 May 2011 09:24:47 GMT

Hello

Problem: One of our staff's Pegasus Mail mailbox has become corrupted. When accessed from a Win 7 PC most new mail when accessed crashes Pegasus as does accessing mail in other folders. I tried removing all .cnm's first and then adding them back gradually, but accessing most of them results in a crash - both in Preview mode and double-clicking the message from non-preview mode.

Installation: Pegasus Mail is installed on a Windows 2008 server, and links the exe are available on staff's desktops. So, the program is always run across the network.

I have moved all mail files out of the account, used Mercury to delete the files, manually deleted the folder, then used Mercury to recreate the account, and moved the files back in - same problem.

When I access the mail account from our Win 2008 server, it works fine. Same from Win XP.

The account was fine until this morning. Pegasus Mail is working fine on other Windows 7 machines on the network.

The following event is saved to the Application Log:

Log Name:      Application
Source:        Application Error
Date:          20/05/2011 09:37:42
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      GREENMAN.htlincs.local
Description:
Faulting application name: winpm-32.exe, version: 4.6.1.0, time stamp: 0x4d532c43
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17514, time stamp: 0x4ce7b8f0
Exception code: 0x0eedfade
Fault offset: 0x0000b760
Faulting process id: 0x10a4
Faulting application start time: 0x01cc16c92da838be
Faulting application path: \\ORION\Pmail\winpm-32.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 6d41803e-82bc-11e0-864a-002564bfee78
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-05-20T08:37:42.000000000Z" />
    <EventRecordID>33022</EventRecordID>
    <Channel>Application</Channel>
    <Computer>GREENMAN.htlincs.local</Computer>
    <Security />
</System>
<EventData>
    <Data>winpm-32.exe</Data>
    <Data>4.6.1.0</Data>
    <Data>4d532c43</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>6.1.7601.17514</Data>
    <Data>4ce7b8f0</Data>
    <Data>0eedfade</Data>
    <Data>0000b760</Data>
    <Data>10a4</Data>
    <Data>01cc16c92da838be</Data>
    <Data>\\ORION\Pmail\winpm-32.exe</Data>
    <Data>C:\Windows\system32\KERNELBASE.dll</Data>
    <Data>6d41803e-82bc-11e0-864a-002564bfee78</Data>
</EventData>
</Event>

Luckily, I have a spare Win XP machine on the network today. I have enabled Remote Desktop and the member of staff is using that to successfully access his mail account.

If anyone has any suggestions about how I might fix this or determine the problem, or insight from the event details above I would be very grateful if you could post them.

Thanks

Re: Pegasus 4.61 with Windows 7 AND IE 9 update (crashes)

RFrey — Thu, 21 Apr 2011 16:27:50 GMT

Pegasus v4.61 / Windows 7 (32 bit) / Service Pack 1 (SP1) / Novell Netware 6.5 / Shared Pegasus Mail Application Directory (Shared with Windows XP Pro users and other Windows 7 Users without SP1 installed)

Given all the above discussion, I elected to uninstall the upgrade to Internet Explorerr 9 (via Windows Control Panel / Programs and Features / View Installed Updates (on the left pane) / (scroll down to:) Microsoft Windows section / right-click "Windows Internet Explorer 9" / Uninstall. It requires a computer restart. Then open up Internet Explorer 8 and make sure it is operational; then retry Pegasus.

I did this on two work stations and all is well.

Note, this was best answer for our situation due to the mixed users accessing the Pegasus application on the shared network directory.

Hopefully, in the coming weeks we will see stable updates to Internet Explorer 9 and/or the IERender.exe so that it can work with IE9 as well as older versions of Internet Explorer at the same time.

How can I restore Pegasus Mail from a no longer booting hard drive?

MadRat — Wed, 06 Apr 2011 09:39:13 GMT

A malware attack left me with a hard drive partition where booting will never again be an option. I can't directly access the partition but I can still copy files off of it. The partition had Windows XP Home and I now have Windows 7 Ultimate 64-bit. I don't know what version of Pegasus Mail was on the XP partition. How can I restore Pegasus Mail under Windows 7 with the same data files, filters and settings, etc.?

Pegasus mail crashed when you try to read a saved e-mail and while waiting inside a folder except New mail

AviB — Thu, 31 Mar 2011 18:02:11 GMT

Hi,

Starting today, Pegasus mail started crashing while trying to open a saved e-mail. I was running Version 4.52 initially and I downloaded V 4.61 and the problem persisted.

I am running Windows 7 Ultimate x64 ad AVG antivirus. The C: is an SSD, but Pegasus mail is loaded onto a SATA 6Gb/s hard drive on E:\

IERenderer is OFF

When I click on an already read e-mail in a folder called Read or Copies Self, Pegasus mail crashes. It seems to crash now when ever you go into a folder and just site there for a short time.

I was able to check the consistancy of the folder & they were OK and I was able to reindex the flders without any problem.

This is the problem details message:

Problem signature:

Problem Event Name: APPCRASH

Application Name: winpm-32.exe

Application Version: 4.6.1.0

Application Timestamp: 4d532c43

Fault Module Name: USP10.dll

Fault Module Version: 1.626.7600.16385

Fault Module Timestamp: 4a5bdb32

Exception Code: c0000005

Exception Offset: 00008dcf

OS Version: 6.1.7600.2.0.0.256.1

Locale ID: 1033

Additional Information 1: 10ac

Additional Information 2: 10ac70d55c839015fbb3c1a8a6e1a066

Additional Information 3: 387c

Additional Information 4: 387cfd8141e792aa9e04491782931b14

Hopefully, there is a solution to prevent these crashes.

Thank,

Avi