Release doesn't change retain count

I am trying to release an object but the retain count doesn't change after the release:
NSLog(@"removeTableViewScreen object retainCount1 [%d]", [myObject retainCount]);
[myObject release];
NSLog(@"removeTableViewScreen object retainCount2 [%d]", [myObject retainCount]);
The output to the console is as follows:
3/3/09 5:23:07 PM removeTableViewScreen myObject retainCount1 [1]
3/3/09 5:23:07 PM removeTableViewScreen myObject retainCount2 [1]
Why wouldn't the release lower the retain count to 0??
Thanks

NSObject Protocol Reference - retainCount
<Edited by Moderator>

Similar Messages

  • Custom UITableViewCell from Interface Builder with retain count 2

    Hi!
    I am creating a customViewCell in my UITableViewController (which I was creating in IB) - the wired thing: it has a retain count of 2! Any hints why?
    UIViewController *c = [[UIViewController alloc] initWithNibName:CellIdentifier bundle:nil];
    GroupCell *cell;// = [[[GroupCell alloc] init] autorelease];
    cell = (GroupCell *) c.view;
    [c release];
    NSDictionary *groupDict;
    NSLog(@"retain count of groupCell: %d, ", [cell retainCount] );
    retain count of groupCell = 2!!
    my cell has no init method, no "retain" nor do I send anywhere a retain to it..

    Hey Alex!
    sommeralex wrote:
    I am creating a customViewCell in my UITableViewController (which I was creating in IB) - the weird thing: it has a retain count of 2! Any hints why?
    Your code is obtaining the retain count by sending the [retainCount|http://developer.apple.com/library/ios/documentation/Cocoa/Referen ce/Foundation/Protocols/NSObjectProtocol/Reference/NSObject.html#//appleref/doc/uid/20000052-BBCDAAJI] message, so this warning in the doc applies:
    Important: This method is typically of no value in debugging memory management issues. Because any number of framework objects may have retained an object in order to hold references to it, while at the same time autorelease pools may be holding any number of deferred releases on an object, it is very unlikely that you can get useful information from this method.
    I think the above is telling us that retainCount returns an accurate number, but that number is useless because we don't know how many releases are pending. E.g., suppose your code has released an object prematurely, so your logical count should be zero. However, if the runtime system has retained the object 5 times at that stage, retainCount will return 5. The point is that all 5 of those retains will be released at some future time not of our choosing.
    You can override retain and release to keep your own count, but I don't know if that count is any more useful than what you get from retainCount.
    I think the only retain count that's any of our business is the number of retains and releases we see in our code. In other words, I think the logical count is much more useful than the real count:
    UIViewController *c = [[UIViewController alloc]
    initWithNibName:CellIdentifier bundle:nil]; // Line A: +1
    GroupCell *cell;
    cell = (GroupCell *) c.view; // Line B
    [c release]; // Line C: -1
    NSLog(@"retain count of groupCell: %d, ", [cell retainCount] );
    Based on the doc for the ['view' property of UIViewController|http://developer.apple.com/library/ios/documentation/UIKit/Ref erence/UIViewControllerClass/Reference/Reference.html#//appleref/doc/uid/TP40006926-CH3-SW2], the view object should be created and retained once when the nib is loaded in Line A (except if no view object is included in the nib, in which case the view would be created and retained once in Line B). The view would then be released once when the view controller is released in Line C.
    So using my arithmetic, the view's retain count is zero after Line C. If that's correct, the only thing saving you from a crash might be one of those system retains we don't know about. You could test my analysis by not giving the view to a table view, then checking to see if it still exists at some point after the end of the current event cycle. You could implement dealloc with a NSLog statement in your custom view to see if and when the view is actually freed.
    Absent any further analysis, I would advise retaining and autoreleasing the view before releasing the controller (or just autoreleasing the controller), to make sure the view lasts until retained by your table view.
    - Ray

  • My iTunes doesn't keep track of my listening history anymore. It doesn't update play counts and default "Recently Played" playlist.

    My iTunes doesn't keep track of my listening history anymore. It doesn't update play counts and default "Recently Played" playlist. But it still tracking plays from my iPhone and syncing them.
    I've tried to repair it with setup file. Nothing's changed.
    Can you help me with that?
    NOTE: Now I tried disabling the crossfade feature and it worked, started to count again. But I like crossfade, I don't want to keep it off.

    I think I got this figured out. The playcount does update, but not how the previous iPod models update their playcount. Instead of immediately updating the playcount right after you finish the song like the older iPod models, iPod Touch keeps the updates in memory. The next time you connect to iTunes it'll sync those playcounts in memory to the actual songs itself, effectively updating the playcount of the songs only after connecting to iTunes. I have set my syncing manually. That's why after connecting to iTunes, my playcounts are updated. BUT it doesn't solve the mystery of my Smart Playlist. Even though in iTunes, the correct songs are listed, in the iPod Touch, it shows the old playlist.
    Don't you just hate that? It was working fine before on non-iPod touch models. Now we have to live with this new bug. I just hope when they release software 2.0 it fixes these bugs and that they *give it for free!* People shouldn't be charged on something they should have gotten as a support!

  • Sub Views and Retain Count

    I am currently creating an app. I am adding sub views to the application like this (it's a feature that switches between a map and a list view):
    MapViewController *mapView = [[MapViewController alloc] init];
    ListViewController *listView = [[ListViewController alloc] init];
    switch (segmentedControl.selectedSegmentIndex) {
    case 0:
    [segmentView addSubview:mapView.view];
    break;
    case 1:
    [segmentView addSubview:listView.view];
    break;
    default:
    break;
    [mapView release];
    [listView release];
    The problem is - that the [listView release] makes my app crash while [mapView release] doesn't. Can someone explain some light on why? MapViewController inherits from UIViewController while ListViewController inherits from UITableViewController.
    EDIT: for some weird reason the editing screws up here but I hope you can read what my problem is regardless.
    Message was edited by: simnie

    simnie wrote:
    ... I just don't get why releasing my list view controller crashes the program while releasing the map view controller does not.
    When you release both controllers at the end of the code block you posted, the retain count for each of those controllers will go to zero, and they will be deallocated, even though--as you pointed out--the view which was added to 'segmentView' will continue to be retained by its superview (i.e. prior to the release of its controller, its retain count was +2, since it had been retained by the controller when the controller and view were created, then retained again by the superview).
    If and when the program crashes depends on whether and when any messages are sent to the deallocated objects. As soon as the table view is added to the superview, it's going to start sending messages to its data source, so if the invalid 'listView' address is also the address of the table view's data source, I would expect an immediate crash. To provoke a crash because of the invalid 'mapView' address, someone would need to send a message to that address.
    I have solved the issue by making the controllers properties in the class instead and releasing them in the dealloc method.
    This is the correct solution. You want each controller to be retained by the respective property setter.
    Btw, I'm not sure why you create both controllers in a method that only seems to use one of them. Since you're now using a retaining property to store the address of each controller you won't leak the memory for the controller when you enter that code multiple times, because the setter for that property will automatically release the previous controller when you replace it with a new one.
    However you might be leaking the memory for the visible view when you enter that code multiple times, since I don't see any code to remove the old view(s). In other words, if you run that code block over and over, it looks like the views you're adding to 'segmentView' will just be layered on top of any previous views, since--as discussed--when the controller is released, the view will still be retained by its superview.
    If the above applies, I would recommend code that only creates each controller one time, as needed. E.g. you could test the property for that controller, and only create a new one if the property is nil. By limiting the number of controllers that get created, you should only have two views at a time, so that problem won't be critical.
    \- Ray
    Message was edited by: RayNewbie

  • Property behaviour curiosity with retain counts

    Hey folks,
    I've been encountering a behaviour with retain counts and properties that I don't expect. I hope someone can clear it up. Assuming this contrived code:
    // Public header
    @interface ObjectB : NSObject
    float m_FloatValue;
    @property(readwrite) floatValue;
    @end
    @interface ObjectA : NSObject
    ObjectB* m_MemberB;
    @property(retain) ObjectB* memberB;
    @end
    // Implementation file
    @implementation ObjectB
    @synthesize floatValue = m_FloatValue
    @end
    @implementation ObjectA
    @synthesize memberB = m_MemberB;
    @end
    Now the trick is that this line of code:
    float valueOfB = anObjectA.memberB.floatValue;
    ... causes m_MemberB to be retained. This seems odd to me, since all I'm trying to do is dig down and pull out the float value of B. Is the default implementation of a (retain)ed property's getter incrementing the retain count? Does it assume I'm storing my reference to that member, so it had better retain it for me to be clever?
    I find this behaviour is causing excess retain counts all over my current app, and I'm having to work around it by implementing my own getters for retained member variables. Am I missing something here, or using something incorrectly? Any information would be much appreciated.
    If it matters, this code is Objective-C 2.0 on the iPhone.
    Thanks!

    I tried your example and reproduced your result, except anObjectA.memberB.floatValue caused m_MemberB to be retained not once, but twice. Then I found that changing from dot to message syntax caused only one retain(??):
    // this causes ObjectB::retain to be called twice
    float valueOfB = anObjectA.memberB.floatValue;
    // this causes ObjectB::retain to be called once
    float valueOfB = [[anObjectA memberB] floatValue];
    The behavior was consistent over several trials with OS 2.1 on both the Simulator and the Device. I also changed the instance variable name to match the property name to rule out a problem with the +@synthesize a=b+ syntax, but this didn't affect the results.
    The advice that's often given in this forum is that observing retain counts is useless since their meaning at any particular stage of execution can't be interpreted (since we don't know how many autoreleases are pending?). In short, "Cocoa knows what it's doing and if you follow the rules you'll wind up with an equal number of retains and releases".
    That said, the above results aren't the kind that inspire much confidence. Hopefully someone who knows what's going on will join this thread soon.

  • Cursor doesn't change to bush when using brush adjustment

    I'm running into an issue when I using the brush adjustment in LR 5.5. The cursor doesn't change from the pointer to the brush cursor. Does any one have a fix for this? I'm running the latest version of LR. I have an 2011 iMac running OS 10.9.4 Any help to solve this issue would be greatly appreciated.

    Same thing here. I also find that Apple Mail is the most frequent offender. Still, like you have mentioned, it is not limited just to mail. This was not a problem for me in Mountain Lion. However, I am noticing that this is a problem for users as far back as 2006 and for every OS release since. It seems that this is not a OS- specific issue. Or if it is, Apple hasnt addressed it in 6 OS releases. This seems like it would be an easy fix. Pretty annoying that it doesnt "just work," right?

  • Satellite Pro P300 - Fn+f5 combination doesn't change the monitor

    On two P300 laptops, we have a problem that the fn+f5 combination doesn't change the monitor layout.
    If you press fn+f5 you see the bar where the different modes are displayed, but if you release the layout stays the same (laptop as single monitor)
    Thanks, kind regards,
    Davy

    Hi
    In my opinion the previous action (installation of catalyst hotkeys and reinstalled the hotkey driver) is the reason why the FN + F5 does not work properly.
    In my opinion you should clean the registry firstly.
    Use CCleaner tool. Its free and cleans the registry.
    Furthermore you should remove the catalyst hotkeys because this can affect the Toshiba FN Hotkey functionality.
    Finally install the Toshiba drivers from the Toshiba page
    In More info (at the right on the Toshiba driver page) you can find all details about the single tools and drivers and what are they for...

  • Column count doesn't match value count at row 1, unknown number of columns

    Hi,
    I am making a program to read data from excel files as the above and store them in tables. I have managed to read all the data from excel files as a string and store them in a table.
    ID Name Salary
    50 christine 2349000
    43 paulina 1245874
    54 laura 4587894
    23 efi 3456457
    43 jim 4512878
    But in my project I have several other files that have same cell that are blank as the above example
    ID Name Salary
    50 christine 2349000
    43 paulina
    laura 4587894
    23 3456457
    43 jim 4512878
    and when i ran the same program i get this exception :
    SQLException: Column count doesn't match value count at row 1
    SQLState: 21S01
    VendorError: 1136The code for creating the table and inserting the values is above:
    private static String getCreateTable(Connection con, String tablename,
                        LinkedHashMap<String, Integer> tableFields) {
                   Iterator iter = tableFields.keySet().iterator();
                   Iterator cells = tableFields.keySet().iterator();
                   String str = "";
                   String[] allFields = new String[tableFields.size()];
                   int i = 0;
                   while (iter.hasNext()) {
                        String fieldName = (String) iter.next();
                        Integer fieldType = (Integer) tableFields.get(fieldName);
                        switch (fieldType) {
                        case Cell.CELL_TYPE_NUMERIC:
                             str = fieldName + " INTEGER";
                             break;
                        case Cell.CELL_TYPE_STRING:
                             str = fieldName + " VARCHAR(255)";
                             break;
                        case Cell.CELL_TYPE_BOOLEAN:
                             str = fieldName + " INTEGER";
                             break;
                        default:
                             str = "";
                             break;
                        allFields[i++] = str;
                   try {
                        Statement stmt = con.createStatement();
                        try {
                             String all = org.apache.commons.lang3.StringUtils.join(
                                       allFields, ",");
                             String createTableStr = "CREATE TABLE IF NOT EXISTS "
                                       + tablename + " ( " + all + ")";
                             System.out.println("Create a new table in the database");
                             stmt.executeUpdate(createTableStr);
                        } catch (SQLException e) {
                             System.out.println("SQLException: " + e.getMessage());
                             System.out.println("SQLState:     " + e.getSQLState());
                             System.out.println("VendorError:  " + e.getErrorCode());
                   } catch (Exception e)
                        System.out.println( ((SQLException) e).getSQLState() );
                        System.out.println( e.getMessage() );
                        e.printStackTrace();
                   return str;
              private static void fillTable(Connection con, String fieldname,
                        LinkedHashMap[] tableData) {
                   for (int row = 0; row < tableData.length; row++) {
                        LinkedHashMap<String, Integer> rowData = tableData[row];
                        Iterator iter = rowData.entrySet().iterator();
                        String str;
                        String[] tousFields = new String[rowData.size()];
                        int i = 0;
                        while (iter.hasNext()) {
                             Map.Entry pairs = (Map.Entry) iter.next();
                             Integer fieldType = (Integer) pairs.getValue();
                             String fieldValue = (String) pairs.getKey();
                             switch (fieldType) {
                             case Cell.CELL_TYPE_NUMERIC:
                                  str = fieldValue;
                                  break;
                             case Cell.CELL_TYPE_STRING:
                                  str = "\'" + fieldValue + "\'";
                                  break;
                             case Cell.CELL_TYPE_BOOLEAN:
                                  str = fieldValue;
                                  break;
                             default:
                                  str = "";
                                  break;
                             tousFields[i++] = str;
                        try {
                             Statement stmt = con.createStatement();
                             String all = org.apache.commons.lang3.StringUtils.join(
                                       tousFields, ",");
                             String sql = "INSERT INTO " + fieldname + " VALUES (" + all
                                       + ")";
                             stmt.executeUpdate(sql);
                             System.out.println("Fill table...");
                        } catch (SQLException e) {
                             System.out.println("SQLException: " + e.getMessage());
                             System.out.println("SQLState: " + e.getSQLState());
                             System.out.println("VendorError: " + e.getErrorCode());
                   }To be more specific the error it in the second row where i have only ID and Name in my excel file and only these i want to store. The third row has only Name and Salary and no ID. How i would be able to store only the values that i have and leave blank in the second row the Salary and in the third row the ID? Is there a way for my program to skip the blanks as empty value?
    Edited by: 998913 on May 9, 2013 1:01 AM

    In an unrelated observation, it appears you are creating new database tables to hold each document. I don't think this is a good idea. Your database tables should be created using the database's utility program and not programmatically. The database schema should hardly ever change once the project is complete.
    As a design approach: One database table can hold your document names, versions, and date they were uploaded. Another table will hold the column names and data types. Another table can hold the data (type for all data = String). This way, you can join the three tables to retrieve a document. Your design will only consists of those three tables no matter how many unique documents you have. You probably should seek the advice of a DBA or experienced Java developer on exactly how structure those tables. My design is a rough layout.

  • Why doesn't iCloud retain hyperlinks or live URL addresses in iCloud contacts?

    Why doesn't iCloud retain hyperlinks or live URL addresses in contacts?
    Hardware/Software Setup Scenario:
    PC with Windows 7 and Microsoft Office 7 Pro at home for which all ISP (Cox Communications) e-mail is integrated with Microsoft Outlook 7. New Apple iPhone 4S linked to MS Outlook Contacts, Calendars, Tasks (Reminders) and Notes via iCloud. All e-mail bypasses iCloud (not needed).
    Problem:
    When initially migrating Microsoft Office 7 Contacts to Contacts in iCloud, Outlook creates a new folder named "Contacts in iCloud," which does synchronize quickly with your iCloud Contacts folder (in Outlook) on your computer at home and your iPhone when you're on the road. That is a great thing to have, and it works well for my calendar, which constantly changes. The unfortunate predicament is that there are some major problems that occur when you convert your Contacts records to iCloud as follows.
    My Contact Notes in Microsoft Office 7, which contain rich formatted text, Microsoft program hyperlinks and live URL addresses (web sites, email addresses, etc.) are all lost because iCloud converts all of it into basic text, rendering the entire Contact Notes box useless. The only way to note a hyperlink is to go back to the web site or email address (if you still have it) and copy the properties in plain text into your notes -- not a reasonable solution.
    An additional problem seen when moving Outlook Contacts to Contacts in iCloud is that the Contact Notes in the new "Contacts in iCloud" are systematically affected by sporadically dropped spaces between words requiring a manual or spell check "cleanup" of every contact -- not reasonable for a folder of approximately 1,000 contacts.
    I have also found that importing my Outlook Contacts into iCloud empties the Outlook "Contacts" folder. Once you have created your new "Contacts in iCloud" folder, the Outlook contacts are gone for good, unless you want to retrieve them from a backup file. The problem is that Outlook will only allow one of these two Contact folders for use; so you’re faced with choosing between syncing your Outlook Contacts manually between your iPhone on iTunes using the USB cable connected to your computer -- not reasonable for someone on the move; or, transfer your contacts to iCloud live with worthless notes for your contacts.
    Can anyone suggest a better work around?

    I'm replying to myself here, but just in case someone else has this problem: I uninstalled the Avery Toolbar and iCloud works on by browser once again. I don't know why or how Avery Toolbar makes a difference, but apparently, it does.  If anyone knows how or why, I'd be interested.

  • Server Monitor and servermgr_xserve retain count in system.log

    We've got 4 Xserves G5s on 10.5.4 all exhibiting this behavior. As soon as we open Server Monitor, we get this message in the log files repeatedly:
    Jul 3 10:28:46 krusty servermgrd[55]: --Module servermgr_xserve's response has retain count of 1.
    Jul 3 10:29:16: --- last message repeated 2 times ---
    It doesn't seem to have any impact on the performance or the server stability so I just ignore it, but I don't want to miss something important if it gets lost in all of these seemingly unimportant messages. Has anyone seen similar behavior and know of a way to stop this logging (short of closing Server Monitor)?

    Did you set up this Xserve as it came from Apple, or did you take an existing 10.5.x image and lay it onto the Xserve? The latter may not have the relevant components in the image... hwmond is an Xserve-only component.

  • ???: Module servermgr_xserve's response has retain count of 1

    I have these suspicious lines in system.log, repeated multiple times:
    Jun 2 23:52:07 xserve servermgrd[55]: --Module servermgr_xserve's response has retain count of 1.
    Jun 2 23:52:37: --- last message repeated 2 times ---
    Anybody know what this is about?

    The phrase "a retain count of 1" is Cocoa programmer talk in reference to retaining/releasing objects in memory. This sounds like a line of debugging code left in by programmers trying to track down a memory leak rather than something evil happening on your server.
    My $.02,
    =Tod

  • [iPhone SDK] property/retain count mystery

    I'm confused as to the behavior of the following code:
    UIViewController *viewController = [[UIViewController alloc] init];
    UITabBarItem *barItem = [[UITabBarItem alloc] initWithTabBarSystemItem:UITabBarSystemItemContacts tag:1];
    printf("1: %d
    ", barItem.retainCount); // is 1 as expected
    viewController.tabBarItem = barItem;
    printf("2: %d
    ", barItem.retainCount); // is 2 as expected
    viewController.tabBarItem;
    printf("3: %d
    ", barItem.retainCount); // expected 2 but got 3
    [viewController.tabBarItem release]; // seems that accessing the tabBarItem increments the retain count, then release decrements it - so this is a noop
    printf("4: %d
    ", barItem.retainCount); // still 3
    output is:
    1: 1
    2: 2
    3: 3
    4: 3
    It appears as if just calling viewController.tabBarItem increments the retain count? (fwiw same thing happens if I call [viewController tabBarItem])
    I know that the tabBarItem @property of UIViewController has the retain attribute, but that means every time I access the property's getter, I'm issuing a retain? I thought it would only retain when set.
    What am I missing here?
    Thanks!

    Thanks for the tips - looks like that's what's happening. Rereading the memory management guide more carefully, under Accessor Methods I see:
    For simple object values, getters and setters can be written in one of the following three ways:
    1. Getter retains and autoreleases the value before returning it; setter releases the old value and retains (or copies) the new value.
    2. Getter returns the value; setter autoreleases the old value and retains (or copies) the new value.
    3. Getter returns the value; setter releases the old value and retains (or copies) the new value.
    The tabBarItem method must be implemented as #1. Still trying to get my head around an example where this would be necessary, but thanks for the help.

  • My macbook pro won't start up. I get the white screen and the grey apple icon   the spinning wheel......and it doesn't change !

    My macbook pro won't start up. I get the white screen and the grey apple icon   the spinning wheel......and it doesn't change !

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.
    To restart an unresponsive computer, press and hold the power button for a few seconds until the power shuts off, then release, wait a few more seconds, and press it again briefly.
    Step 1
    The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
    There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
    a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
    b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
    c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
    d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
    Step 2
    If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
    Step 3
    Sometimes a startup failure can be resolved by resetting the NVRAM.
    Step 4
    If a desktop Mac hangs at a plain gray screen with a movable cursor, the keyboard may not be recognized. Press and hold the button on the side of an Apple wireless keyboard to make it discoverable. If need be, replace or recharge the batteries. If you're using a USB keyboard connected to a hub, connect it to a built-in port.
    Step 5
    If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
    Step 6
    Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
    Step 7
    If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
    Start up in safe mode. Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
    Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
    If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
    If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
    Step 8
    Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
    This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
    Step 9
    If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.  
    Step 10
    Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
    Step 11
    Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
    Step 12
    This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
    Step 13
    If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

  • My weather doesn't changes according to time

    My weather doesn't changes according to time as after 12:00 am it will remain the same day

    Try:
    - Reset the iOS device. Nothing will be lost       
    Reset iOS device: Hold down the On/Off button and the Home button at the same time for at
    least ten seconds, until the Apple logo appears.
    - Reset all settings      
    Go to Settings > General > Reset and tap Reset All Settings.
    All your preferences and settings are reset. Information (such as contacts and calendars) and media (such as songs and videos) aren’t affected.
    - Restore from backup. See:                                                
    iOS: How to back up                                                                                     
    - Restore to factory settings/new iOS device.                     
    Also, the US daylight saving time starts tonight. Sometimes the iOS has problems around DST

  • The html container doesn't change size according to the width of the website, but instead the width of the window.

    As stated. The html container doesn't change to match the content on the website (like Internet Explorer does), it changes to match the screen size. That way, when you scroll horizontally, elements disappear because the html container is the size of the screen and in a fixed position.
    Example (my problem): http://www.elitepvpers.com/forum/web-development/1847846-question-css-html-width-problem.html
    Happens with most websites such as...
    http://google.com/
    http://co.91.com/index/
    http://www.w3schools.com/
    http://stackoverflow.com

    locked by moderator as dulicate

Maybe you are looking for