Closed Bug 223614 Opened 21 years ago Closed 19 years ago

Termination of Mozilla probably when sending information to Yahoo! Mail (like respond a message).

Categories

(Core Graveyard :: Java: OJI, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: bruno_nicolas, Assigned: joshua.xia)

Details

User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.5b) Gecko/20030827 Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.5b) Gecko/20030827 Mozilla caused an arror in the module or application called jpinsp.dll. This appended when surfing and sending mail to the yahoo! mail server. Twice today the 24th October 2003. Reproducible: Sometimes Steps to Reproduce: 1. 2. 3. This crash caused to lose data because all the tabs are closed by the violation. I did not quote SEVERITY because it did not happen all the time.
Could you possibly test 1.5 final or a current nightly?
OS: other → OS/2
Mozilla doesn't have a jpinsp.dll Can you look on your system and see where this DLL is?
26.10.2003 Bug happened once again. After sending mail in Yahoo! Netscape agent started and then the error message that Mozilla has caused an error in JPINSP.DLL shows up. I have reinstalled the latest Mozilla client : Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.5) Gecko/20031007 I hope this info will be useful. Bruno
Are you ignoring me? Read my last comment. Find JPINSP.DLL on your system. It's not mozilla.
This isn't an OS/2 issue. It's Win9X jpinsp.dl appears to be a Java DLL
OS: OS/2 → Windows 98
reporter: do you install talkback builds? if not, could you install talkback? otherwise, a drwtsn32 log would be the next best thing.
Assignee: general → joshua.xia
Component: Browser-General → Java: OJI
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.