EVE Information Portal

I should probably mention: This doesn't cover the web-browser that we have built in to Eve (it's a different process) - I wouldn't even consider making that mandatory, since you could be interacting with a third party website that we have no business knowing anything about. Most of the rest of the cases of doing stuff in the Eve client already require you to interact with our servers.

This change won't be ready for the patch tomorrow since it will need to be both done and tested.

Will this report when the entire computer hangs up and becomes unresponsive and needs a reboot? I had one last week while playing Eve. I was going to write a bug report but I couldn't think of anything out of the ordinary that was happening when it crashed like that. CPU, GPU, case temps within norm...

If your entire system freezes it won't be possible for the bug reporting mechanism to fire, so, no.

Though in general a complete system lock like this is rarely ever the fault of an application, but an indication of a lower-level issue with your system (faulty drivers, bad power, flakey RAM, RF interference, etc).

In the short term, if you're worried about this feature then the best workaround would be to block your computer from accessing http://crashes.eveonline.com

This won't cause any issues with Eve, but it will mean that we won't be able to see and fix your crashes.

Thank you. While not as good as implementing opt-in from the start, this is a refresh change from the wall of silence we used to receive from CCP from such concerns.

Also, I want to say that I have no objections to providing crash information to CCP, in fact I believe it to be a valuable tool for developers to be able to quickly identify and kill bugs. What I do like is to be given the option of submitting the crash data, and reviewing it so that I can confirm that what is being sent is actually what is supposed to be sent. After I've verified this I have no issues about 'rubber stamping' the report until the next patch, during which I like to review the information again.

Then again, I understand I'm in the minority, but still, asking permission is just the polite thing to do in any event.

What operating system are you using. Win = Sisilauncher a big win
Mac I think is getting a launcher too- hopefully the new cider engine was requred before it could be released.

CCP an update please

Confirming the current Sisi build runs on a Mac.

CCP, what about bugs that do not result in crashes? Many times these bugs pop up and its unclear what I did that caused them, or how to recreate them, or even if I do figure out how to recreate them, its a low chance that they will happen.

Are you planning on adding any tools that lets me save some sort of log data right after I see a bug? Something I do not have to prepare before hand, as I usually do not know beforehand when I will hit a bug. I'm thinking of some background process that's always running and keeps a running log of the last 5 minutes, and when I get a bug I can save that log and send it off to you.

Good idea on the automatic crash reporter.

Now how about a rolling snapshot log file that can be on 24x7 without filling a disk? Bug hunters and Devs are always wanting a log to see what set of circumstances caused an error (crash or not). If the user has some idea of how to consistently reproduce a error that is no problem.

But when users have an intermittent bug that refuses to perform on demand and is not so frequent that its sure to happen in the next couple hours - there is a problem. Neither users nor bug hunters want to deal with hours and days worth of log files.

When tracking an irksome issue, I personally would not mind a log file that ran continuously but only preserved only the most recent 30 minutes. Something that I can use like a screenshot (and probably with a screenshot) when I see an intermittent error occur. Something to which bug hunters can easily send a log reconfiguration file if the first log file fails to identify the fingerprints of the cause. Something users can reset to defaults with a button push that does not reset all of user cache. (Sounds sort of like what many routers and firewalls do for log files.)

Users should not be asked to fill their disks with huge log files (do I even have the space), edit off the tail end of the file (does the user even have proper software to edit to massive log files), or dig in the guts of EVE to configure log files. But bug hunters do need all the info that is practical.

EVE does not need more "Yes your screenshot shows an important error. But without a log file or user observed 100% reproducible steps, CCP bug hunters have to ignore your report."

Say that automatic crash reporter could even send in that last 30 minute log automatically during next start up if a user option button was set. Of course not all errors crash the client so an easy manual attach needs to be available.

Indeed.

Replace iteration with recursion. Infinite loops cause StackOverflowExceptions. Win.

(In all honesty don't do that.)