krotseal.blogg.se

1. #League of legends mac client quit unexpectedly Patch
2. #League of legends mac client quit unexpectedly code

10.4 - Addressed an issue causing the social panel and chat window to break in Champ Select if certain actions (removing a friend, being removed, being blocked) were taken.10.3 - Sorting by "Milestones Passed" in the Collection now works properly.10.3 - Sorting the Collection no longer defaults to reverse-alphabetical order when changing sorting filters.10.3 - The Store icon is now properly highlighted when selected after using a Hextech Chest in loot.10.3 - Middle-clicking links no longer breaks the client.10.1 - Profile background changes are now properly displayed to other players.10.1 - Fixed an issue that sometimes caused the client to crash when regaining internet connection after having been disconnected for over a minute.10.1 - Fixed an issue that sometimes caused the League logo next to the "Play" button to disappear.10.1 - The client's position no longer resets after finishing a game.In the meantime, here's a list of some of the client bugs the team has addressed on a per-patch basis since the beginning of the year:

#League of legends mac client quit unexpectedly Patch

Starting with patch 10.13, you'll see client bugfixes in their own section of the League patch notes. The client team has been opportunistically tackling tons of bugs over the previous few months. Speaking of bugs and crashes, let’s talk about some recently-shipped fixes.

#League of legends mac client quit unexpectedly code

Our plan for now is to continue the consolidation work for at least the next couple of months, as we believe there are meaningful long-term benefits of reducing the number of plugins and ember apps-by cleaning up the overall code environment, we're making it easier to solve bugs, memory leaks, and crashes. (See the most recent client blog for a deeper discussion about this topic, in the section labeled "The Trouble With Affinity.") We're hopeful that we'll start to see more improvement to bootstrap times over the next few patches, especially now that we've developed a new solution that allows us to more intelligently specify which plugins load in whenever you boot up your client. Shuffling around big chunks of code and rewiring plugins could cause some unforeseen issues if we're not careful-but so far that doesn't seem to be happening. We actually consider this to be a moderate success, given the risks inherent to the work we're doing. Below you can see a chart showing how that metric has been tracking over time:Īs you can see, bootstrap times have mostly been holding steady over the past couple of months. One of the ways we've been measuring the impact of our work is by tracking the amount of time it takes for the client to boot up. Leaner code equals better performance and also results in a client that's easier for devs to maintain. If you're reading the chart above, you're probably thinking okay, but how exactly does this impact the client's performance? The answer to that is complicated, but at high level: fewer plugins and Ember apps means more efficient client code. The chart below shows the total count of plugins and ember apps over time. We've continued to make progress toward this goal. Ember apps help drive the client's user interface. Plugins-for those who don't know-are tools that allow us to break the client's code up into useful chunks. As we said in our first client blog, we believe that the best way to solve some of the client's performance issues is by consolidating and reducing the number of plugins and ember apps in the client.