Chapter 162 The man behind the incident

Speaking of which, compared to the time and space of Lin Hui's previous life, this time and space is only only seven years old.

But it gives Lin Hui a very retro feel.

When Lin Hui was searching for news about Apple's "frequency reduction gate" incident, he flipped through several forums where time and space fans gathered.

I discovered that one of the best posts actually discussed the tombstone mechanism and pseudo-backend.

Σ(っ°Д°;)っTombstone mechanism? Pseudo backend??

What an old topic.

In a few years, even experienced fans will probably have forgotten these things.

The tombstone mechanism, also known as the pseudo-background, is a program running rule in the mobile operating system.

When the previous task is forced to be interrupted, such as the moment when you press the Home button to return to the main interface.

The system will record the current state of the application, and then the program will be frozen (completely suspended), just like recording the event on a tombstone.

When recovery is needed, the program is restored to the state before the interruption based on the content on the tombstone.

One such mechanism is the tombstone mechanism, which is commonly found in mobile devices, platforms with limited memory or power resources.

Both limited memory and limited power seem to be distinctive features of early Apple mobile phones.

Therefore, this tombstone mechanism is particularly favored by Apple and was applied to early Apple mobile phones.

On top of this mechanism, Apple also opened a backend interface.

Allow the application to continue running for 10 minutes after entering the background. Whether the screen is turned on or the screen is turned off, the application will be suspended for 10 minutes. Once the time is up, the application will be suspended immediately.

The tombstone backend saves the scene when closing the program and restores it the next time it is started, giving people the illusion of a backend.

Although this operation has certain rationality, those who play games are not fools.

This almost Emperor's New Clothes-style shenanigans will be seen through if it's a bit serious.

Judging from the attitudes of users on these forums, the pseudo-backend mechanism is very much criticized by gaming enthusiasts.

In the next few years, it would be almost difficult to imagine that Pingchun still had this dark history.

In short, from the perspective of seven years later, Pingchun at this time is not that powerful at all.

It's like a shabby hut.

All it takes is a kick and...

Uh, but this specific matter still needs careful consideration.

After all, Pingcheng’s size and history lie there.

It's not something that Lin Hui can handle casually now.

Let’s go back to the fact that the memory calls involved in the game “Hill Climb Racing” often exceed 300MB.

Although he is aware of the problem, Lin Hui has no intention of making any adjustments in this situation.

The so-called 512MB random access memory like 4,4s.

Lin Hui really didn't know what kind of adjustments he should make to accommodate him.

Perhaps these phones were quite classic when they were first released.

But after all, technology products are updated very quickly.

Lin Hui had nothing to feel guilty about.

There are so many game manufacturers in later generations. I have never heard of any game manufacturer adjusting the game because players complained that the game consumed too much memory.

Times are moving forward after all.

What's more, Lin Hui would have to change a lot of underlying things if he wanted to make further adjustments, which would be very troublesome.

As for whether or not I should inform Pingchen about the crux of my thinking.

Lin Hui didn't think it was necessary.

Apple's technical staff are not idiots either.

The crux should soon be discovered.

Nowadays, the raging discussion from the outside world mainly points to Apple's frequency reduction.

Instead of pointing at Lin Hui.

How to proceed with this kind of thing should be a question that Pingcheng should consider.

Don't worry about the matter being your own.

If you respond rashly to this kind of thing, you will easily be pushed to the front by Pingchun and take the blame.

This is not the first time Pingcheng has done this.

Lin Hui didn't want to take the blame for no reason.

…

Now Lin Hui's focus is still on the workflow software.

Since this software has a demo, Lin Hui can easily finish the code part.

However, this does not mean that Lin Hui can directly put this software online.

When it comes to this software, Lin Hui still needs to conduct some internal testing.

There is no need for Lin Hui, the polished commander now, to conduct beta beta testing.

But it is still necessary for the minimum alpha internal testing.

The reason why the Nanfeng APP that Lin Hui worked on before did not need to go through the internal testing.

To a large extent, this is because the software was developed by Lin Hui based on mature applications.

In addition, for Nanfeng APP, what Lin Hui cared about at that time was the algorithm inside the software, not the software itself.

But now with workflow software, what Lin Hui cares about is the software itself.

As for why the games that were previously launched did not go through internal testing?

This is because Lin Hui basically has corresponding development experience in these games in his previous life.

Therefore, those previous games did not need to go through any internal testing at all.

Although Lin Hui has ready-made ideas for workflow software.

But in essence, it is still an almost completely redesigned software that Lin Hui has not developed before.

In this case, some testing is definitely needed.

Lin Hui was thinking about alpha internal testing.

Pingchun (here refers to Pingchun China) is also busy.

When it comes to technical reasons, Pingcheng has long understood the ins and outs.

In fact, the "frequency reduction gate" thing was just starting to take off.

Pingchun organized technical personnel to conduct corresponding analysis.

Pingchun quickly found the crux of the problem:

——The memory called for some scenes in the game "Hill Climb Racing" is too large.

As a result, there will be a less smooth experience on some early models.

When Apple's technical staff conducted analysis, they were not limited to the problem itself, but also analyzed the game.

The game "Hill Climb Racing" is just an ordinary physics racing mobile game.

Although Lin Hui himself claims that this game is developed based on racing characteristics and has a real physics engine.

But to be honest, Apple's technical staff don't really approve of the physical characteristics involved in this game.

It's like Newton came to life with anger.

The key is that it is not elegant at all, and the dynamic design is completely inconsistent with Pingchun's aesthetic.

But this kind of game has gained the love of players.

From the player's perspective, this is a simple game.

Players can race on various tracks with just two keys.

From the perspective of game functions, it is not difficult to implement such an application.

This is also something that puzzles Apple’s technical department.

Such a simple application is nothing more than a complicated map.

Why do we need to call hundreds of megabytes of memory at every turn?

Even though there was something they didn’t understand, Apple’s technical department reported the problem to Apple’s relevant marketing department almost immediately.
To be continued...