Xiamen north station to Sports Center
Publish: 2021-05-08 20:42:07
1.
bus line: Metro Line 1 → 855, the whole journey is about 27.6km
1. Take Metro Line 1 from Xiamen north station, pass 18 stations, and reach Hubin East Road Station
2. Walk about 520m to Lvjiayuan community station
3. Take bus 855, pass 2 stations, and reach Sports Center West Station (or take bus 857)
4. Walk about 670m, Arrive at Xiamen Sports Center
2. No.80 Zhangdian bus terminus - ecation and examination center
bus terminus - Jiazhuang - zhangbo road - Zhonggu - Zhaocun - Haojia - Merchants - ecation and examination center
departs at 6:30 and ends at 17:20
bus terminus - Jiazhuang - zhangbo road - Zhonggu - Zhaocun - Haojia - Merchants - ecation and examination center
departs at 6:30 and ends at 17:20
3. Hello, No.80 bus, the first bus is 6:20, about 50 minutes to the ecation and examination center, the whole journey is 5 yuan, 40 minutes (the bus terminus is in Jiazhuang)
now most bus lines are bus terminus, such as No.2, No.7, No.12, No.34, No.35, No.51 (East), No.51 (West), No.58, No.76, No.96, No.108, No.121, No.125, No.126, No.132, No.139 159, 160, 222, 251.
now most bus lines are bus terminus, such as No.2, No.7, No.12, No.34, No.35, No.51 (East), No.51 (West), No.58, No.76, No.96, No.108, No.121, No.125, No.126, No.132, No.139 159, 160, 222, 251.
4. No.80 Zhangdian bus terminus ecation and examination center
bus terminus Jiazhuang zhangbo road Zhonggu Zhaocun Haojia business ecation and examination center
bus terminus Jiazhuang zhangbo road Zhonggu Zhaocun Haojia business ecation and examination center
5. It is handled by Zibo Transportation Bureau, and the regulations in the regulations on the management of road transport practitioners are as follows:
the qualification examination for operating road passenger and freight transport drivers is organized and implemented by the municipal road transport management institutions with districts, and the examination is organized once a month
address of Zibo Transportation Bureau: 140 Xincun West Road
nearby bus stop:
Municipal Transportation Bureau - bus stop
passing bus: No.35, No.90, No.96, No.126, No.132, No.6
the qualification examination for operating road passenger and freight transport drivers is organized and implemented by the municipal road transport management institutions with districts, and the examination is organized once a month
address of Zibo Transportation Bureau: 140 Xincun West Road
nearby bus stop:
Municipal Transportation Bureau - bus stop
passing bus: No.35, No.90, No.96, No.126, No.132, No.6
6. The possibility should not be big, unless driving schools like Tongbao can test in their own driving schools, but this situation is extremely slim... After August 13, there was another "simulation test of light use at night for small cars in subject 3", so after the examination of subject 3, we can only go to the ecation and examination center
7. The owner of the building can go to the traffic management office of Zhangdian District Transportation Bureau located at No. 1, Xincun road or Shanquan road to apply for registration. Your driver's license must be C or above, with driving experience of more than three years and junior high school ecation; After you sign up, you can take the certificate and pay the tuition fee at the traffic technical school on Zhangnan road. The tuition fee is about 500 to 600, and you can study for about a week. The examination includes theory examination and security examination; About two weeks after passing the examination, you can get the certificate at the registration office.
8. It's not a report. It's your files that may have been transferred there. However, most schools don't put the files directly in the talent center. If they are in a city, they usually send them to the sub district office or something. You can ask
after graation, the society will not care about you. You have to find a job by yourself, and no one will care whether you report or not
after graation, the society will not care about you. You have to find a job by yourself, and no one will care whether you report or not
9. 1. Run demo
first download a demo to implement the prepared memory leak: leak app
download it, open it and run it. The program is a list of sushi rolls. Try to choose a few lines in it. It should collapse when you choose the second line. Screenshot of crash:
the crash is stopped at the crash site. You know the crash site, but you don't know the cause of the crash
2. Set nszombieenabled
this is an "exc"_ BAD_ Access error. We turn on the Xcode option: "nszombieenabled.". In crash, you may be given more information
setting steps: 1
2: check
run in the red box, and select the cell according to the operation. Crash again, this time you will see an additional error message in the output window:
2012-11-28 13:22:08.911 propmemfun [2132:11303] * * - [cfstring respondstoselector]: message sent to deallocated instance 0x713ebc0
roughly means: Send a message to the released memory. That is to say, using the released memory is equivalent to using "wild pointer" in C language.
look at the crash statement. Sushistring should be OK. It is initialized from stringwithformat. That's it_ Last sushiselected< br />_ Lastsushiselected points to sushistring, which is an autorelease variable. At the second click, sushistring has been released, so crash is done. What is that_ The last sushiselected is reserved for use. The code is modified as follows:
_ lastSushiSelected = [sushiString retain];
running, this time does not crash
3. Analyze the memory leak (Shift + Command + b)
if the app doesn't crash, see if there is a memory leak. With Xcode's analyze, we can analyze where there is a memory leak.
after analysis, we can see that:
it prompts that alertview has not been released. If there is a memory leak, we will release
[alertview release]
after further analysis, this problem is solved
4. Using the leaks tool of instruments
to analyze memory leaks, we can't find out all the memory leaks. Some memory leaks are only generated ring runtime and user operation. Then we need to use instruments
press the above operation, after the build is successful, jump out of the instruments tool and select the leaves option. At this time, the sushi program will also run. After selecting the items in the list and dragging, the tool will display the following effect:
as you may guess, the red column indicates that the memory is leaked. How can we see where the leak is through this tool
first press the red round button on the toolbar to stop the tool monitoring memory activity. Select leaf, then click the middle cross and select call tree.
at this time, the options of call tree in the lower left corner can be selected. Select invert call tree and hide system libraries, and the display is as follows:
at this time, the specific code of memory leak is found, and the red box on the right specifies which method has memory leak
as long as you double-click on these methods, you will jump to the specific code. Ha ha, isn't it very convenient
here should be a prompt that 100% memory will leak
6. Solve the memory leak problem
if the problem is found, then solve it
about: tablev iew:didSelectRowAtIndexPath Analyze its memory process:
sushistring variable is created by autorelease, and its reference count is 1.
this line of code increases the reference count to 2_ lastSushiSelected = [sushiString retain];
at the end of this method, the autorelease of sushistring takes effect, and the reference count of this variable is reced to 1
when you execute tablev again iew:didSelectRowAtIndexPath In this way_ Lastsushiselected is assigned a new pointer, the old one_ The reference count of lastsushiselected is still 1 and has not been released, resulting in a memory leak
how to solve it
in_ lastSushiSelected = [sushiString retain]; The original release was OK before:
[_ lastSushiSelected release];< br /> _ lastSushiSelected = [sushiString retain];
about: tablev iew:cellForRowAtIndexPath
this is obvious. Sushistring is not released after alloc and init. You can use stringwithformat to call autorelease. The code is as follows:
nsstring * sushistring = [nsstring stringwithformat: @ & quot;% d: %@", indexPath.row, sushiName];
OK, the leaks are all fix, and then use tools to analyze them. At this time, you can click, drag and operate again, and there will be no memory leaks. Indicates that the memory leak is blocked.
first download a demo to implement the prepared memory leak: leak app
download it, open it and run it. The program is a list of sushi rolls. Try to choose a few lines in it. It should collapse when you choose the second line. Screenshot of crash:
the crash is stopped at the crash site. You know the crash site, but you don't know the cause of the crash
2. Set nszombieenabled
this is an "exc"_ BAD_ Access error. We turn on the Xcode option: "nszombieenabled.". In crash, you may be given more information
setting steps: 1
2: check
run in the red box, and select the cell according to the operation. Crash again, this time you will see an additional error message in the output window:
2012-11-28 13:22:08.911 propmemfun [2132:11303] * * - [cfstring respondstoselector]: message sent to deallocated instance 0x713ebc0
roughly means: Send a message to the released memory. That is to say, using the released memory is equivalent to using "wild pointer" in C language.
look at the crash statement. Sushistring should be OK. It is initialized from stringwithformat. That's it_ Last sushiselected< br />_ Lastsushiselected points to sushistring, which is an autorelease variable. At the second click, sushistring has been released, so crash is done. What is that_ The last sushiselected is reserved for use. The code is modified as follows:
_ lastSushiSelected = [sushiString retain];
running, this time does not crash
3. Analyze the memory leak (Shift + Command + b)
if the app doesn't crash, see if there is a memory leak. With Xcode's analyze, we can analyze where there is a memory leak.
after analysis, we can see that:
it prompts that alertview has not been released. If there is a memory leak, we will release
[alertview release]
after further analysis, this problem is solved
4. Using the leaks tool of instruments
to analyze memory leaks, we can't find out all the memory leaks. Some memory leaks are only generated ring runtime and user operation. Then we need to use instruments
press the above operation, after the build is successful, jump out of the instruments tool and select the leaves option. At this time, the sushi program will also run. After selecting the items in the list and dragging, the tool will display the following effect:
as you may guess, the red column indicates that the memory is leaked. How can we see where the leak is through this tool
first press the red round button on the toolbar to stop the tool monitoring memory activity. Select leaf, then click the middle cross and select call tree.
at this time, the options of call tree in the lower left corner can be selected. Select invert call tree and hide system libraries, and the display is as follows:
at this time, the specific code of memory leak is found, and the red box on the right specifies which method has memory leak
as long as you double-click on these methods, you will jump to the specific code. Ha ha, isn't it very convenient
here should be a prompt that 100% memory will leak
6. Solve the memory leak problem
if the problem is found, then solve it
about: tablev iew:didSelectRowAtIndexPath Analyze its memory process:
sushistring variable is created by autorelease, and its reference count is 1.
this line of code increases the reference count to 2_ lastSushiSelected = [sushiString retain];
at the end of this method, the autorelease of sushistring takes effect, and the reference count of this variable is reced to 1
when you execute tablev again iew:didSelectRowAtIndexPath In this way_ Lastsushiselected is assigned a new pointer, the old one_ The reference count of lastsushiselected is still 1 and has not been released, resulting in a memory leak
how to solve it
in_ lastSushiSelected = [sushiString retain]; The original release was OK before:
[_ lastSushiSelected release];< br /> _ lastSushiSelected = [sushiString retain];
about: tablev iew:cellForRowAtIndexPath
this is obvious. Sushistring is not released after alloc and init. You can use stringwithformat to call autorelease. The code is as follows:
nsstring * sushistring = [nsstring stringwithformat: @ & quot;% d: %@", indexPath.row, sushiName];
OK, the leaks are all fix, and then use tools to analyze them. At this time, you can click, drag and operate again, and there will be no memory leaks. Indicates that the memory leak is blocked.
Hot content