Publicly accessible bug reporting & serious UI updates

If Adobe want to make Livecycle a serious platform for developers, then why not open up the bug reporting database the same as has been done with Flash Builder / SDK, Coldfusion, etc? http://bugs.adobe.com/. Most Livecycle devs can navigate themselves around Jira and responsibly search for or log a bug or feature request.
And at the same time get some people from the Photoshop / Flash Builder IDE UI team to work on Workbench and Designer. The UI's are in desperate need of updates to bring them in line with the current UI's that Adobe provide. Designer looks and feels like it has been left in last decade somewhere compared to Photoshop or Flash Builder.

Chaosmachine,
Emu does not have any official forums. I will take a look into this to see if there is anything I can suggest. You can also contact their tech support through their web page, www.emu.com.
Jeremy

Similar Messages

Driver update and bug reporting t

I am wondering what users of this forum think about the idea of a responsi've bug reporting mechanism along the lines of the ati catalist programme in which bugs get reported to the drivers department.
the purpose of this would be for the following
to enable users to report to creative bugs in the software
To enable creative to then identify (and acknowlege) problems early and work towards resolving any that appear.
To enable creative to then offer incremental or updated software on a timely basis.
This would improve users perception of creative as a company that is responsi've to its users and enable problems to be dealt with promptly.
Please try and keep comments relvant to the original post as I think it might be interesting to gauge users perception of this idea
Andy

Vista?
Ooh boy.
http://support.apple.com/kb/TS1538
Good luck.

Bug Report E71 - Post (serious) bugs here.

Hi,
Maybe it's wise to have a dedicated bug report topic for the E71.
So not discussions here .. just USEFULL reports.
Bug #1 :
Situation:
- I am having a sip internet-call (native SIP client) with an Asterisk server.
- put the call on 'standby' (by menu Options)
- i press the 'Options' softkey again
- phone freezes. Only battery removal can restart it.
(it also freezes after doing some random key presses .. which i can't remember exactly .. but the standby is not stable.)
Bug #2:
- please fix color-settings for the camera . There is 'purple' all over.

501.21.001 on RM-357 (E71-2) Since upgrading to 501, I've had two major problems. 1) rarely (it's only happened twice), the SMS application will hang when attempting to reply to a message. The original message stays on the screen and nothing will let me out of the app. The phone will respond to the power button, however, and seems to work fine after a reboot. 2) battery life and/or battery meter is terrible. Battery meter will stay near the top then suddenly drop to 2-3 bars remaining. Energy Profiler seems to confirm my power usage is about where it used to be (drawing about 0.12W with the screen off and Gravity running in the background). Phone will then reach 1 bar and give "battery low" warnings, but I'm not convinced the battery is truly low. Last night I was on one bar for over two hours, Gravity was left running, I send and received a few texts, and I was connected to my in-car bluetooth for about 25 minutes, and the phone did not die. On the original firmware, I would never have made it through all that on one bar, which makes me think the bug is with the battery meter, not the battery life itself.

Bug Report: The keyboard focus doesn't automatical...

Bug Report: When a conversation window opens, the focus doesn't automatically land in the chat entry text field.
Since the new interface for Skype was introduced officially in Skype 7.0, there is a bug with the system/keyboard focus for a new conversation window. When Skype is in "Split Window View" and each new conversation automatically pops up in a separate window, the system/keyboard focus doesn't land in the chat entry edit field. Instead, the user has to press Shift+TAB a couple of times, to move it there and reply to the chat message received. This especially problematic for screen reader users, who rely on keyboard navigation. This mainly occurs when a new conversation is started with an incoming message, but it sometimes occurs when moving the focus out of that conversation window and later back in it again (while it is still opened).
Steps to reproduce it:
1. From "View" menu, activate the "Split Window View", if it is not already enabled.
2. From Tools -> Options -> IM & SMS -> IM settings, enable "Open a new window when I receive a new message in Split Window View", if it is not already enabled.
3. From Tools -> Options -> Advanced, activate "Enable accessible mode", if it is not already enabled.
4. Activate the "Save" button, to save the changes.
5. Close all windows, related to Skype. You may keep only the main window opened.
6. Tell someone to send you a chat message. When the message arrives, Move the system focus to the conversation window in question, preferably with Alt+TAB. The system/keyboard will not land in the chat entry edit field as it did in Skype 6.21 and earlier and as it should by default, but in some unknown place in the window.
7. Move the system/keyboard focus in the chat entry edit field and keep it there.
8. Switch to another window, preferably from another application.
9. With Alt+TAB, switch back to the window of the opened Skype conversation. There is a chance that the system/keyboard focus will not land in the chat entry edit field as it did in Skype 6.21 and earlier and as it should do by default, but again in some unknown place in the conversation window. But that is harder to reproduce.
Test environment:
- Operating system: Windows 8.1 Pro N, 64-bit, in Bulgarian with all locale settings set to "Bulgarian".
- Skype version: 7.0.0.102 for Desktop.

This is a known problem, but Skype have not given us an estimated time for a fix.
Traditionally, Skype updates have been roughly monthly, so we are due a new version sometime soon. Many of us here are hoping that is has a bunch of fixes for the UI, the focus problem being one of them.
Sean Ellis - uses Skype chat for serious work
Click here to read my blog post on Skype 7 and basic principles of GUI design

Bug Report: New conversation window stills the sys...

Bug Report: Skype Desktop: New conversation window stills the system/keyboard focus.
When the UI is in multi-window mode and a conversation window pops up (due for example to a newly received chat message), that window steals the system/keyboard focus, even though it appears in a minimized state in the Windows taskbar. And this should not happen by default, because it is impractical (especially for screen reader users). And it didn't happen in Skype 6.21 and earlier. But since the new UI was introduced officially in Skype 7.0, it started happening constantly.
Steps to reproduce it:
1. From "View" menu, activate the "Split Window View", if it is not already enabled.
2. From Tools -> Options -> IM & SMS -> IM settings, enable "Open a new window when I receive a new message in Split Window View", if it is not already enabled.
3. From Tools -> Options -> Advanced, activate "Enable accessible mode", if it is not already enabled.
4. Activate the "Save" button, to save the changes.
5. Close all windows, related to Skype. You may keep only the main window opened.
6. Move the system focus to another application.
7. Tell someone to send you a chat message. When the message arrives and the conversation window pops up minimized in the Windows Taskbar, everything seams to be as it should. A few seconds after that however, the system/keyboard focus gets moved to that new conversation window, even though it is neither restored/maximized (it is minimized), nor it is visible on the screen (except as a button in the taskbar).
Actual results:
When a new conversation window pops up in the Windows taskbar, it stills the system/keyboard focus to itself from the currently focused application.
Expected results:
Skype's popping up new conversation windows should not still the system/keyboard focus to themselfs from the currently focused application.
Test environment:
- Operating system: Windows 8.1 Pro N, 64-bit, in Bulgarian with all locale settings set to "Bulgarian".
- Skype version: 7.0.0.102 for Desktop.

This is a known problem, but Skype have not given us an estimated time for a fix.
Traditionally, Skype updates have been roughly monthly, so we are due a new version sometime soon. Many of us here are hoping that is has a bunch of fixes for the UI, the focus problem being one of them.
Sean Ellis - uses Skype chat for serious work
Click here to read my blog post on Skype 7 and basic principles of GUI design

Reported serious regression in 5.0u14 2 months ago with no response

Hi there,
I posted a regression bug to the bug database on the 13th December, and have had not had any feedback to know whether they accepted the bug and cannot find it in the database.
Is there any way to confirm either way whether my bug was accepted? Do you usually get an email if your bug was either accepted or rejected?
The bug submission process seems to provide very poor feedback. You don't get any sort of email acknowledgment of the submission, or any type of tracking number so that you can check whether your issue has been accepted. It seems pretty poor.
The issue we found was a serious regression in the behavior of a Java app on Windows XP. If the Java application is running when the user performs a shutdown or logout, the application does not shutdown and Windows displays the "This program is not responding." and the user is prompted to "End now?". This blocks the logout process.
Our application runs in the task-tray on 10's of thousands of desktops in schools and colleges around the world. So this is a very serious problem for us. When we shipped update 14 (which fixed another problem we were encountering), it caused this even worse problem. We had to re-release the software with an older JRE. This continues to be a problem for us because some customers run the software with their own JRE installs.
This behavior can be seen by running this very simple program below using Java 5.0u14. Simply run it, and then logout of Windows and the error will be blocked. If you run the identical program on 5.0u13 then the logout works properly.
import javax.swing.JFrame;
import javax.swing.SwingUtilities;
public class SwingTest {
public static void main(String... args) throws Exception {
SwingUtilities.invokeAndWait(new Runnable() {
public void run() {
JFrame frame = new JFrame("title");
frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
frame.setVisible(true);
I submitted all of this in my bug report on the 13th December. It would be great if I new if someone at Sun was listening!!
Regards,
Matt

Canon posted new drivers for some of their printers - including the MP470 - at the start of November. These specifically say they support 10.5 (though I had no problem using older drivers for my MX310 in 10.5.0).
Get them from:
http://www.usa.canon.com/consumer/controller?act=ModelInfoAct&tabact=DownloadDet ailTabAct&fcategoryid=334&modelid=15403
or:
http://www.canon.com.au/products/allin_one_printers/all_in_one_printers/mp470support.aspx
I only upgraded to 10.5.1 (from 10.5.0) last night so haven't tested printing again. I hope this helps.

BUG REPORT FIRMWARE 5.1.7 PLEASE FORWARD TO SUPERVISOR....

BUG REPORT FIRMWARE 5.1.7 PLEASE FORWARD TO SUPERVISOR.
The spa-3102 has the following two bugs.
When the unit sends a hook-flash to the fxo port it:
a) does not send the hook flash to the fxo port for PSTN Hook Flash Len: Instead it uses a very short pulse of about 100ms or 1/10 of a second. It should honor the PSTN Hook Flash Len configurable parameter of .2 – 1.5 seconds.
b) Does not change the line voltage from –7 (off-hook) to –48(on-hook) during a flash-hook to the fxo port. Instead it varies the voltage only by about 2.5 volts.
This was reported as early as June 07 to linksys support. It is reported they agreed and would fix in the next firmware release. There is info that firmware 5.2 being released and is this fix in 5.2 and how can I get it.

Although the problem is still not solved, at least I now know WHY the problem is happening... and Apple's Firmware Update is NOT to blame!
Through a series of coincidences, I was actually lucky enough to get in touch with the engineers in Apple's Airport firmware division, and they were helping me to nail down this problem.
Turns out that Apple takes great PRIDE in the fact that they are one of the VERY FEW manufacturers who make routers that behave properly in this regards: they SPECIFICALLY test for their Airport Extreme routers to allow you to connect to servers behind the NAT by way of the public WAN IP address of the NAT box. This is the way that apparently the NAT/DHCP specification is SUPPOSED TO WORK! You're SUPPOSED to be able to connect this way, if you so desire.
So what was causing the problem on my network, then?
Something I hadn't thought about... the Vonage Linksys RTP300 router that we're using for our Vonage VoIP service. Turns out that this router does NOT support clients behind the NAT connecting to servers behind the NAT by way of the public WAN IP address.
Linksys is to blame, not Apple!
And apparently, this feature may have actually been working in an earlier
firmware update, but apparently, Vonage AUTOMATICALLY pushes firmware
updates to RTP300's, apparently without user notification:
<http://www.vonage.com/help.php?article=1066&category=90&nav=5>
And a forum thread on vonage-forums.com seems to indicate that the 1.00.60 firmware in the RTP300 started getting pushed to customer units on or before 1/26/06, making it less than a month after Apple shipped the 5.7 firmware update for AirPort Extreme Base Stations:
<http://www.vonage-forum.com/ftopic10915.html>. So if the problem cropped up then, it's possible that I accidentally attributed it to Apple when really the RTP300 got a firmware update around then too which may have broken this feature (assuming it was working before then).
Power Mac G4 QuickSilver Dual 800 MHz Mac OS X (10.4.4)

BUG report - Inconsistent IR settings in Builder

Apex 4.0.2
Most of the reports used in the App Builder have been converted to use Interactive reports which is great. But I find that the IR settings are not consistent across all the reports. I had reported this during the tryapexnow.com beta phase. Now that we can use the new apex_application_install API to load up the Builder apps into our own workpace so we can review how they are built, the Region Utilities > Update Interactive Report Settings page shows this. Or just run the query
select
page_id, name, allow_save_rpt_public, show_finder_drop_down, show_display_row_count, show_search_bar, show_search_textbox, show_actions_menu, show_select_columns, show_rows_per_page, show_filter, show_sort, show_control_break, show_highlight, show_computation, show_aggregate, show_chart, show_notify, show_group_by, show_calendar, show_flashback, show_reset, show_download, show_help
from apex_040000.wwv_flow_worksheets
where flow_id=4000My main annoyance is the "Save Report Public" checkbox. The IR saved report list shouldn't be cluttered with all the report settings saved by all the workspace developers.

Please submit an official bug report to Adobe at:
http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Alexander.
Canon EOS 400D (aka. XTi) • 20" iMac Intel • 12" PowerBook G4 • OS X 10.4 • LR 1 • PSE 4

Bug Report: Shortcuts for Adjustments in 3.1

I have verified that bug with a brand new test account (Aperture 3.1 and OS 10.6.4 with latest Pro Update):
- Make an adjustment to an NEF-file
- save that adjustment as a preset
- assign a keyboard shortcut to that specific adjustment
Switch to the next NEF-file and make your usual adjustments:
- initiate that shortcut to apply the already saved preset/adjustment
All of a sudden, all already applied adjustments are set back to defaults!!!!
To sum up:
Shortcuts are presently not useable!
Bug Report was filed!
Any observations???

I got it myself. My shortcut combination contained the option key. That causes AP to replace any adjustments already made to the image. You have to use a keyboard short cut combination without the option key.
The question is, why AP 3.1 is not smart enough to refuse such a combination??? In version 3.0.x everything worked fine!!!

Bug report on Japanese Ruby

Just a bug report on some ruby word options on Japanese script
「泳」for 「泳ぐ」never accept any ruby.
「三味線」should be reas as 「しゃみせん」and suggested option actually includs the correct reading. However, the actual ruby you will get is 「ざみせん」.
Hope they are fixed in the next update.

For Apple to see your report, you should use
http://www.apple.com/feedback

Bug report: ignore not working

Bug report: ignore in the forum here not working
I set some SPAM users to 'ignore' - still can see their SPAM.
Please fix it.

The "Ignore a community user" feature will only block private messages received from other community users. See also the community help here: http://community.skype.com/t5/help/faqpage/faq-category-id/pm#pm
Is that what you are referring to or do you expect this also to hide public messages posted by these users (which is not what it is currently designed to do).
If you should spot content on the community that is violating our Community Guidelines please use the "Report inappropriate content" link from the "Post Options" menu next to the message. These abuse reports will then be reviewed by our moderation team.
Follow the latest Skype Community News
↓ Did my reply answer your question? Accept it as a solution to help others, Thanks. ↓

Bug report, Beta 2.12 Standard Edition

Bug report: redundant, confusing, and apparently erroneous calls to
jdoPreClear
and jdoPostLoad. Note in output the null name in the third iteration.
Hi,
A lot of information being sent. Sorry, but I think you'll find it
helpful. I expected the exact same sequence of calls to jdoPreClear
and jdoPostLoad on the 2nd and third iteration. In fact, since,
retain values is true, and no changes are being made, I expected that
jdoPreClear and jdoPostLoad would not be called at all on the 2nd and
3rd iteration.
David Ezzio
Using 2.12 Beta, standard edition
Business method uses one PM. Configured to datastore transaction,
retainValues == true, non-TR == false, and non-TW == false.
The business methods open a transaction and leave it open.
The client calls commitTransaction() to close the open
transaction.
Two persistent objects, Widget and Box. Each implement
InstanceCallbacks and put out a message in jdoPreClear ("will be
made hollow") and in jdoPostLoad ("has been made persistent-clean").
The Widget has a reference to its Box. The number in parenthesis
is the sequence number obtained from the object ID.
Business methods implementation:
public ArrayList getWidgetsByName(String name)
Transaction trans = pm.currentTransaction();
if (!trans.isActive())
trans.begin();
Collection c = (Collection) widgetsByOneName.execute(name);
ArrayList aList = new ArrayList(c);
widgetsByOneName.close(c);
return aList;
public void commitTransaction()
Transaction trans = pm.currentTransaction();
if (trans.isActive())
trans.commit();
Output: from three loops that:
call findWidgetsByName("Maxi-Widget")
list the widgets returned
call commitTransaction()
finding Maxi-Widgets ...
Widget Maxi-Widget (650) has been made persistent-clean
Box Large (652) has been made persistent-clean
Widget Maxi-Widget (650): Box Large (652) at location Top Shelf
Widget Maxi-Widget (709) has been made persistent-clean
Box Large (710) has been made persistent-clean
Widget Maxi-Widget (709): Box Large (710) at location Middle Shelf
Widget Maxi-Widget (708) has been made persistent-clean
Box Large (713) has been made persistent-clean
Widget Maxi-Widget (708): Box Large (713) at location Top Shelf
Widget Maxi-Widget (700) has been made persistent-clean
Box Large (717) has been made persistent-clean
Widget Maxi-Widget (700): Box Large (717) at location Top Shelf
Widget Maxi-Widget (707) has been made persistent-clean
Box Large (716) has been made persistent-clean
Widget Maxi-Widget (707): Box Large (716) at location Top Shelf
Finding them again
finding Maxi-Widgets ...
Widget Maxi-Widget (650) will be made hollow
Widget Maxi-Widget (650): Box Large (652) at location Top Shelf
Widget Maxi-Widget (709) will be made hollow
Widget Maxi-Widget (709): Box Large (710) at location Middle Shelf
Widget Maxi-Widget (708) will be made hollow
Widget Maxi-Widget (708): Box Large (713) at location Top Shelf
Widget Maxi-Widget (700) will be made hollow
Widget Maxi-Widget (700): Box Large (717) at location Top Shelf
Widget Maxi-Widget (707) will be made hollow
Widget Maxi-Widget (707): Box Large (716) at location Top Shelf
Finding them yet again
finding Maxi-Widgets ...
Widget null (650) will be made hollow
Widget Maxi-Widget (650) has been made persistent-clean
Widget Maxi-Widget (650): Box Large (652) at location Top Shelf
Widget null (709) will be made hollow
Widget Maxi-Widget (709) has been made persistent-clean
Widget Maxi-Widget (709): Box Large (710) at location Middle Shelf
Widget null (708) will be made hollow
Widget Maxi-Widget (708) has been made persistent-clean
Widget Maxi-Widget (708): Box Large (713) at location Top Shelf
Widget null (700) will be made hollow
Widget Maxi-Widget (700) has been made persistent-clean
Widget Maxi-Widget (700): Box Large (717) at location Top Shelf
Widget null (707) will be made hollow
Widget Maxi-Widget (707) has been made persistent-clean
Widget Maxi-Widget (707): Box Large (716) at location Top Shelf
-- All done!

Due to better understanding on my part, and the fixes in Beta 2.2, the
issues raised in this thread are put to rest.
Abe White wrote:
>
We'll investigate further. Stay tuned...
"David Ezzio" <[email protected]> wrote in message
news:[email protected]..
Abe,
Actually, it doesn't make sense. The first iteration shows
jdoPostLoad is called just prior to using the fields of Widget and Box.
After the commit, the instances are not cleared. So far, so good.
In the second iteration, we see that jdoPreClear is called, but
jdoPostLoad is not called. Yet the values are there for use during the
call to Widget.toString() and Box.toString() within the iteration. How
did that happen?
On the third iteration, now the value of name is null, but last we
looked it was available in the second iteration. Other than that, I
agree that the third iteration looks ok, since it is being cleared and
loaded prior to use. But in the jdoPreClear, the values should be there
since the values were used in the previous iteration and are not cleared
at transaction commit due to retainValues == true.
David
Abe White wrote:
David --
I believe the behavior you are seeing to be correct. Section 5.6.1 of
the
JDO spec outlines the behavior of persistent-nontransactional instancesused
with data store transactions. As you can see, persistentnon-transactional
instances are cleared when they enter a transaction; thus the calls to
jdoPreClear. When the default fetch group is loaded again (like whenyou
access the name of the widget) a call to jdoPostLoad is made.
You are seeing the name of one instance as 'null' in the third iterationof
your loop because the instance has been cleared in the second iteration,and
the jdoPreClear method is not modified by the enhancer (see section10.3).
Make sense?

Bug report: ube_ipa: internal error when compiling with -xO5

When compiling imlib2-1.1.2, one source file causes compilation to fail with the following error message:
ube_ipa: internal error
cc: ube_ipa failed for loader_tiff.c
The command which fails is (probably wrapped):
cc -DHAVE_CONFIG_H -I. -I. -I.. -I. -I.. -I../src -I../loaders -I../libltdl -I/usr/X11R6/include -I/usr/openwin/include -I/opt/csw/include -I/opt/csw/include -I/opt/csw/include -g -fast -xarch=386 -xstrconst -v -xildoff -xO5 -c loader_tiff.c -KPIC -DPIC -o .libs/loader_tiff.o
Changing -xO5 to -xO4 works around the problem. The source file in question is imlib2-1.1.2/loaders/loader_tiff.c
Patch 112756-10 has been applied, and doesn't correct the problem. GCC doesn't have any problem compiling the file.
A quick note to any Sun employees reading this: it took me 45 minutes to find somewhere to submit this bug report. Searching sun.com for "submit bug report" turned up many forum postings where people asked "Where do I submit bug reports?", a bug report form for Sun One Java Studio, and not much else. It might be in your interest to make submitting bugs easier.

Internal errors, such as the one you encountered, are generally considered compiler bugs. They indicate that the compiler reached an unexpected state and therefore bailed out. I opened bug 20703141: internal error: pic_relocs(): hh reltype? to investigate. I see the same error message emitted by the current Studio development release; I will update this thread if I find a work-around.
Thanks,
Mark

Sending a bug report on the OS and a sleep mode problem.

I find the bug button in Safari really convenient for sending Apple bug reports. And when other applications crash, you usually get an error dialog with a button to send a bug report. But sometimes problems arise that require reporting, but which don't fall in either of these categories. It would be very handy to have a bug "button" for the OS, or perhaps just a menu selection in the Finder menu bar that invokes a bug report dialog box. I know you can dig around and find the URL for Apple's bug report web page, but I am always forgetting it -- I suppose I could just bookmark it, but then I'd just have to dig around in all the bookmarks to find it. Better would be a utility built-in to the OS for sending bug reports (like Safari's). It could also automatically transfer necessary info about the OS rev and such.
The problem I had was this. I have a script that puts my iMac to sleep. I put the script alias on the task bar and a single click puts the computer to sleep (easier than using the menu). Unfortunately, I sometimes click it by mistake when I am trying to click an adjacent icon in the task bar, and the Mac starts going through its cycle to enter sleep mode and is impervious to anything I do to try and cancel it. I tried pressing the space bar continuously to prevent it from going to sleep, but that did not work. Worse, when it went to sleep and I woke it up again, the task bar would not appear, clicking on app windows did not activate them, Finder menus could not be selected, etc. The cursor would move, but I could not do anything else. (I wish now I had noted if the clock in the menu bar was still advancing, but I didn't think to do that.) I powered down the iMac from the power key and rebooted. Things are working fine now.
I wanted to send a bug report on this, but realized that unlike Safari, there was no button or menu selection for doing that. So here I am.
Any suggestions are welcome.
TIA,
Drake

[email protected]
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Bug report, how do I find out what is wrong?

my computer keeps getting bug reports stuck all over the desktop. When I print them it is 3 pages long and I dont know how to use the information from it. It only occurs when my son is using Runescape an online game. My son says he has reported all the errors when the computer prompts him to. I did find an Bug Report that seems to be associated with this problem. Our computer did shut down occasionally also, but since I switched the location of the new memory I added it has not continued. The reason I am checking with this website is because this is where the reports are going. The first part of the error report from my computer is this:
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x809D50E
Function=JVM_FindSignal+0x10882
Library=C:\PROGRA~1\Java\J2RE14~1.2\bin\client\jvm.dll
Current Java thread:
     at r.a(Unknown Source)
     at r.a(Unknown Source)
     at client.t(Unknown Source)
     at client.B(Unknown Source)
     at client.a(Unknown Source)
     at a.run(Unknown Source)
     at client.run(Unknown Source)
     at java.lang.Thread.run(Unknown Source)
And the last part of the report reads this:
Local Time = Fri Mar 04 21:38:29 2005
Elapsed Time = 58
# HotSpot Virtual Machine Error : EXCEPTION_ACCESS_VIOLATION
# Error ID : 4F530E43505002EF
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
# Java VM: Java HotSpot(TM) Client VM (1.4.2-b28 mixed mode)
What do I need to do to fix this problem? Could it be Runescapes issue? Is there other information that is more important to this? I really appreciate any help I can get with this problem. And I am sorry for being so long. I have included the Bug Report I found that is an almost exact duplicate of our issue.
Thank you again, Linda Peterson.
COPIED FROM BUG REPORT SEARCH AREA
Bug ID: 5092499
Votes 1
Synopsis IA64 - EXCEPTION_ACCESS_VIOLATION on IA664 W2003
Category java:runtime
Reported Against 1.4.2_05
Release Fixed
State In progress, bug
Related Bugs
Submit Date 26-AUG-2004
Description OS: Windows2003 [5.2.3790]
Chip: Itanium 2
JVM: Sun 1.4.2_05-b04 64-bit server VM
Error message:
EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x84D5F10
Function=[Unknown]
Library=C:\j2sdk1.4.2_05\jre\bin\server\jvm.dll
Error ID: 4F530E43505002EF
xxxxx@xxxxx 10/5/04 20:02 GMT
Work Around N/A
Evaluation Post tiger
xxxxx@xxxxx 2004-09-02
Comments
Include a link with my name & email
Submitted On 05-FEB-2005
JavaJava13 Hey just wondering. Java is used for runescape on my computer, and it seems to be constantly crashing lately. Not only the game is crshing, it seems to even take down the whole computer with it. Sometimes the computer restarts and I get an error message.
"Your system has recovered from a serious error"
Java continues to add error reports to my desktop with this code: 4F530E43505002EF
Anyone help?

try checking with runescapes FAQ/tech support. I play
WC3: RoC and i only got that same memory location
error(0xc0000005). I got that memory error when I
used a no-cd third party program when they upgraded
the server. So, my advice is check on the FAQ for
errors and ask your son if he is using
ANY third party programs.The 0xc0000005 error is a standard error on Windows that can occur for any number of reasons.
It means something in the application tried to access memory to which windows knows the application should not be accessing.

Publicly accessible bug reporting & serious UI updates

Similar Messages

Maybe you are looking for