Enter Login System Auto Logout in sec back to Login menu.. and so on..*
hi, Im recently on mac world. so I dunno what I have todo with this trouble.
my mac just fine before I press the power button 8 seconds to turn off the system freezes. now every time I enter a password and log into my account, the system logout and back on the "login menu" without any confirmation.
now use the guest account to make an emergency admin account. that's where I sent this post. I hope there is help for me in concrete. I need my main account. all data and my life there. please help.
system.log
Oct 16 03:07:54 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:07:54 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:07:54 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:07:55 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:07:55 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:07:55 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:07:55 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:07:55 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:07:55 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:07:56 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:07:56 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:07:56 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:07:56 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:07:57 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:07:57 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:07:57 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:07:58 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:07:58 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:07:58 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:07:58 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:07:59 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:07:59 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:07:59 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:00 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:00 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:00 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:00 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:01 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:01 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:01 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:02 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:02 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:02 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:02 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:03 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:03 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:03 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:04 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:04 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:04 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:04 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:05 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:05 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:05 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:06 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:06 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:06 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:06 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:07: --- last message repeated 1 time ---
Oct 16 03:08:07 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:07 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:08 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:08 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:08 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:08 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:09 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:09 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:09 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:10 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:10 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:10 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:10 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:11 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:11 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:11 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:12 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:12 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:12 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:12 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:13 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:13 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:13 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:14 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:14 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:14 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:14 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:15 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:15 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:15 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:16 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:16 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:16 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:16 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:17 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:17 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:17 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:18 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:18 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:18 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:18 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:19 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:19 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:19 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:20 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:20 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:20 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:20 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:21 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:21 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:21 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:22 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:22 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:22 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:22 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:23 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:23 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:23 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:24 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:24 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:24 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:24 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:25 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:25 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:25 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:26 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:26 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:26 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:26 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:27 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:27 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:27 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:28 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:28 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:28 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:28 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:29 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:29 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:29 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:30 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:30 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:30 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:30 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:31 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:31 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:31 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:32 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:32 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:32 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:32 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:33 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:33 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:33 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:34 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:34 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:34 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:34 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:35 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:35 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:35 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:36 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:36 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:36 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:36 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:37 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:37 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:37 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:38 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:38 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:38 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:38 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:39 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:39 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:39 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:40 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:40 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:40 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:40 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:41 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:41 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:41 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:42 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:42 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:42 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:42 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:43 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:43 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:43 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:44 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:44 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:44 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:44 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:45 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:45 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:45 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:46 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:46 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:46 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:47 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:47 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:47 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:47 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:48 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:48 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:48 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:49 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:49 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:49 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:49 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:51: --- last message repeated 1 time ---
Oct 16 03:08:50 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:50 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:51 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:51 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:51 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:51 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:52 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:52 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:52 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:52 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:52 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:52 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:53 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:53 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:53 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:53 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:54 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:54 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:54 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:55 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:55 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:55 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:55 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:56 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:56 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:56 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:57 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:57 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:57 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:57 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:58 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:58 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:58 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:59 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:08:59 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:08:59 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:08:59 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:09:00 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:09:00 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:09:00 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:09:01 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:09:01 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:09:01 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:09:01 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:09:02 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Oct 16 03:09:02 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:09:02 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: *** set a breakpoint in malloc_error_break to debug
Oct 16 03:09:03 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: 业务监控线程正在轮询
Oct 16 03:09:03 Fadhil-Parewangi-Mac [0x0-0x59059].www.ztemt.com.cn[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated
Oct 16 03:09:03 Fadhil-Parewangi-Mac ZTE Wireless Terminal[546]: ZTE Wireless Terminal(546,0xb0314000) malloc: *** error for object 0x5c212d4d: pointer being freed was not allocated\n*** set a breakpoint in malloc_error_break to debug
Here is a pic of what is happening when the computer auto logs out. This was after I reset smu and pram. Yes, I do have a custom loginwindow image... I have been using this image since OS 10.5.
Similar Messages
-
I have to enter login information and "secret phrase" every time Firefox starts up.
I have to enter login information and "secret phrase" for Sync every time Firefox starts up. Sync tells me I am using a new computer, which isn't the case. This is the same computer I set up Sync with.
What am I/is Sync doing wrong?There could be several things.
Does everyone using the computer have their own user profile?
Check the history settings. Is it set to remove cookies?
Type '''about:preferences#privacy''' <Enter> in the address bar.
The button next to '''History,''' select '''Use Custom Settings'''.
Some Anti-Virus, Disk Cleaning, and other programs will remove things
from your browsers. Including history and cookies. -
Enter login manager and X respawn issue
Wondering if anyone else has this. I have a login for myself and one for my wife and 'normal' people who don't want/know how to use a tiling WM and firefox-pentadacytl, and want to have a graphical login manager. SLiM caused too many hard crashes where I'd lose the keyboard. GDM and KDM have too much cruft and LXDM is even less stable. Enter looked good, but on logout from openbox (not ScrotWM), tty7 locks up and I'll get the "X respawning too fast: disabled for 5 minutes message" in my logs/tty1.
With SLiM it looks like this is an auth. file and/or xorg.conf error from what I've read. I've been relying on X to auto-config and don't have an xorg.conf.
Where do I want to start to work around this?
I'll post my initab and Xorg logs in a second or two.
Relevant inittab lines:
# Boot to console
#id:3:initdefault:
# Boot to X11
id:5:initdefault:
rc::sysinit:/etc/rc.sysinit
rs:S1:wait:/etc/rc.single
rm:2345:wait:/etc/rc.multi
rh:06:wait:/etc/rc.shutdown
su:S:wait:/sbin/sulogin -p
# -8 options fixes umlauts problem on login
c1:2345:respawn:/sbin/agetty -i -8 38400 tty1 linux
c2:2345:respawn:/sbin/agetty -8 -s 38400 tty2 linux
c3:2345:respawn:/sbin/agetty -8 -s 38400 tty3 linux
c4:2345:respawn:/sbin/agetty -8 -s 38400 tty4 linux
c5:2345:respawn:/sbin/agetty -8 -s 38400 tty5 linux
c6:2345:respawn:/sbin/agetty -8 -s 38400 tty6 linux
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
x:5:respawn:/usr/bin/enter >/dev/null 2>&1
Xorg.0.log:
Oct 23 15:53:35 thimkbrick init: Switching to runlevel: 5
...skipping...
Oct 29 19:14:00 thimkbrick dhcpcd[621]: wlan0: leased 192.168.5.11 for infinity
Oct 29 19:14:00 thimkbrick dhcpcd[621]: forked to background, child pid 645
Oct 29 19:18:12 thimkbrick init: Switching to runlevel: 5
Oct 29 19:18:12 thimkbrick enter: Starting X server. [...x7 more]
Oct 29 19:18:12 thimkbrick init: Id "x" respawning too fast: disabled for 5 minutes
Oct 29 19:18:12 thimkbrick enter: Starting X server.
Oct 29 19:18:18 thimkbrick enter: Server timed out [...x8 more]
Oct 29 19:18:23 thimkbrick enter: Logging in user
Oct 29 19:23:13 thimkbrick enter: Starting X server. [...x8 more]
Oct 29 19:23:13 thimkbrick init: Id "x" respawning too fast: disabled for 5 minutes
Oct 29 19:23:13 thimkbrick enter: Starting X server.
Oct 29 19:23:19 thimkbrick enter: Server timed out [...x8 more]
Last edited by nathan28 (2011-10-29 23:28:56)Took another pass at the login manager thing again today. Just tried to re-install xorg-xkbcomp, to little apparent effect.
Logging out of ScrotWM works. Logging into Openbox (via my other user's login) works. Attempting to log out of openbox, either with the r-click logout or with $ openbox --exit, drops me to an X root window and enter does not reappear without # killall X or #telinit 3 followed by #telinit 5.
Is is possible that this is a result of the
exec ck-launch-session dbus-launch --exit-with-session openbox-session
line in the regular user .xinitrc? Otherwise I'm at a loss for ideas besides hacking the Enter code.
Mostly giving up on this for now.
Last edited by nathan28 (2011-12-26 19:04:48) -
after downloading and installing the program it won't let me validate it. I close the program and launch it again but now when I sign in nothing happens. It just sits there.
seanare wrote:
Thank you, as I noted here, your post was the key to my getting a Windows 8 SecureBooting setup on a W530.
In the case of Windows 8, I needed to copy the files away, reformat my USB key as FAT32 and copy the files back, and viola I was able to boot from my USB install media with the BIOS set to only boot UEFI. From there, there rest was easy (for Windows 8, the copying and renaming is not necessary, the key is having a FAT32 partition on the USB media, rather than an NTFS one; the EFI files are already in the right location).
Thank you again good sir.
You are welcome... and I'm happy that the change of the file system helps with windows 8 too. Thanks for confirming that.
abvasili
I'm just a volunteer. I like to help others where I can. Do my ideas work? I hope so. o_O
Who helped you today? Do not forget to thank him.
My hardware: TP x120e 0596-2ru. Windows 7, sp1, 64Bit, English, installed in UEFI mode. -
No place to enter login name and password
After recent update there is text boxes to enter user name and password for signing in with the skype name but they are read only. Even mouise can not point to any of those controls.What is going on?I am using skype long time and this is the first I see anything like that.Is it usual microsoft attempt of humor?
What version of Windows are you on (XP, Vista, Windows 7, Windows 8 )? Is it 32-bit or 64-bit? http://support.microsoft.com/kb/827218 What is the version of Internet Explorer installed on your computer? In Internet Explorer go to Help -> About Internet Explorer. P.S. Please, don’t say that you are not using Internet Explorer. This is irrelevant. Skype depends on Internet Explorer.
-
System Preferences does not open in Dock, Apple menu and in apps?
I'm experiencing an issue with System Preferences. One day the I noticed that the Icon changed to a white page with the "Applications" "A" on it. Since then, I have not been able to launch the System Preferences in my profile. In my wife's, it works fine.
It changes in the Dock, or in the stacks pop-out window? If the latter, try double clicking it from within /Applications directly.
-
Any ideas?
Thanks, but there has to be someway through ITunes or something to make this not happen. It used to not do this so something with an update or something must have changed a setting somewhere. Anyone else have any ideas?
-
Unlock with Admin to Auto-Logout
Looking for a way to have the system auto-logout if the screen is unlocked by an administrator. So if User1 is logged in and an admin unlocks the screen, User1 is logged out. This is enterprise standards that have to be met.
If FastUserSwitching is enabled, is there a way to have a login script check how many users are logged in and to log out if more than one are? I've tried messing around with the USERS and LOGNAME commands but they don't seem to work in a shell script like they do with direct input in terminal.
It'd be best to achieve this without any third party apps and only with scripts.
Anyone have any ideas?
Thank!I don't think this is possible. To my knowledge, unlocking a screen doesn't trigger any system event or other process to which any script can be attached.
-
Auto logout time different per users
Hello
we are using almost all modules in ECC. So we have 2 kinds of SAP users, the administrative ones and the operational ones.
The administrative ones is using SAP all the day by creating purchase orders, process orders or recording control results by example. When they make an activities in SAP they can completed the task without any interruption.
But we have as well operational users who are using SAP to make physical activities like to place pallet in the warehouse with WM functions and to weight a drum from the PI-sheet in PPPI.
The auto logout is after 15 minutes of inactivity and I don't find how to set it up per users. In deed, the operator in production needs time between each weighing meaning stick label, remove the previous drum, take the new one, write information on the paper batch record, ... The time between 2 actions in SAP is more than 15 minutes. So the operator is automatically logout between each weighing and it takes around 2 minutes to log again and reload the Pi-sheet. By example, to weight 46 drums the operator will lost more than 1,5 hour. It's not acceptable by the production.It increases the production time of 16%.
How can I set up a auto logout time to 15 minutes or less for the administrative users and 1 hour for the production users located in a protected area ( no access by external people) ?
thanks in advance for your answer
regards
V Noirot
PPPI team leadHi,
You can increase the logout time for the endusers. But the power users, throughout the day they will be using the system. This time increase will not affect much on the power users. If you are saving some productive hours by increasing this time out means, you can do this. But it will act similar for both the users.
regards,
V. Suresh -
Hi altogether,
is there anybody who knows how to disable auto-logout? I've searched the profiles and roles, but evething seems to be o.k., in the default-role every option is 'unlimited'.
Thanks a lot
best regards
AndreasYah, I found the official metalink note:
1. Navigate to the EM OMS $ORACLE_HOME/sysman/config directory.
2. Make a backup copy of the emoms.properties file and then open the original file with a text editor. Go to the bottom of the file and add the line: oracle.sysman.eml.maxInactiveTime=60. This will set the idle session time to 60 minutes before disconnecting the session.
3. Stop the Management Service and restart it.
emctl stop oms
emctl start oms
This setting will increase the timeout to 60 minutes instead of the default 15 minutes. -
When i type in my correct password on the login screen and press enter it just goes to a blue screen for a few seconds then goes back to the same login screen again, please i need help?
You can take some of the steps here, #4, #5 or even trying a #18
Step by Step to fix your Mac
but I suspect your going to first have to create a data recovery drive
Create a data recovery, undelete boot drive
to get your data off the machine,
then do a #20 to eliminate the bad sectors as that's why your getting the "pinwheel" it's getting a delay reading from the drive, right when your trying to log in too, what a bad spot for it to happen.
Step by Step to fix your Mac -
Screen Pixalation when using Sleep and Auto Logout problems. OS bug?
Original Thread here: http://forums.macrumors.com/showthread.php?t=1295058
Thread Tools
Search this Thread
Display Modes
Dec 21, 2011, 01:01 PM
#1
gswilder
macrumors regular
Join Date: Oct 2007
iMac Sleep Problem Waking - Screen Black & Pixelization
Have a new BTO 27" iMac I received a couple of weeks ago. Of course it is running Lion 10.7....
I am having a screen problem "waking" my iMac. (I also have this problem randomly on my MB Air - mid 2011 model)
After the iMac is in true sleep mode
(I have it set to enter a password after sleep mode)
Screen is blank/off
I "wiggle" my mouse or trackpad
Screen is still blank (sometimes it may display my screen saver, but the screensaver is frozen)
If I start moving the mouse or trackpad, it starts "un painting" the black screen. You can see whatever is supposed to be on the screen, such as the logon "button".
It is really wierd. Like a black "overlay" is painted on the resume from sleep screen. As I move my mouse or trackpad, it is basically erasing the black, to show what is underneath. Each movement of the mouse, erases a small black square.
I usually move my mouse around the middle of the screen to uncover the logon button. Press the logon button. The screen magically reappears as normal. I enter my password and system logs back on normally.
It only seems to be when the iMac is in really deep sleep mode. If the screen is just blank for an hour or so. I move the mouse/trackpad, and the logon screen is immediately displayed normally.
Any thoughts or recommendations?
Thanks to all in advance.
Greg
0
Dec 23, 2011, 12:17 AM
#2
gswilder
Thread Starter
macrumors regular
Join Date: Oct 2007
UPdate
Still experimenting.
If certain programs are running (ie Firefox), then I don't have a problem coming out of deep sleep. It gives me a message when I reenter my password, that Firefox prevented the system from logging off.
Does that additional information help? It is a really annoying problem. And since I have it on my MBA, I am concerned it is more widespread. Does anyone else have this issue?
0
Dec 24, 2011, 09:18 PM
#3
UNCHeelYeah
macrumors newbie
Join Date: Dec 2011
Black Screen and "Erasure" with Mouse.
I am having this same problem. I am using the Mac OS X Lion 10.7.2, not using a screen saver, and it happens sporadically upon trying to wake my iMac from sleep mode. The screen is black, and as you move the mouse over the screen, it "erases" the black, like the opposite of a blackboard, to reveal the login name and picture underneath. After that everything works fine. There is no pattern to this that I can discern (e.g. - happens every fifth time, only happens when a program isn't running etc.). It appears random, but is uber annoying, and behaves like a virus. I have Norton Antivirus, and it updates daily, and upon scanning states no virus is found. I also do system scan with MacKeeper, and it scans, says system is excellent. Something is definitely going on, I just wish I knew what it was. If anyone has any knowledge of this, any solution or insight would be greatly appreciated! Thanks!
0
Dec 25, 2011, 12:29 PM
#4
GGJstudios
macrumors G4
Join Date: May 2008
Quote:
Originally Posted by UNCHeelYeah
It appears random, but is uber annoying, and behaves like a virus. I have Norton Antivirus, and it updates daily, and upon scanning states no virus is found.
That's because there are no Mac OS X viruses. You should uninstall Norton. You don't need 3rd party antivirus apps to protect your Mac from malware. Macs are not immune to malware, but no true viruses exist in the wild that can run on Mac OS X, and there never have been any since it was released 10 years ago. The only malware in the wild that can affect Mac OS X is a handful of trojans, which can be easily avoided with some basic education, common sense and care in what software you install. Also, Mac OS X Snow Leopard and Lion have anti-malware protection built in, further reducing the need for 3rd party antivirus apps.
Mac Virus/Malware Info
Quote:
Originally Posted by UNCHeelYeah
I also do system scan with MacKeeper, and it scans, says system is excellent.
You don't need MacKeeper, either. You really don't need "cleaner" or "maintenance" apps to keep your Mac running well, and some of these apps can do more harm than good. Most only remove files/folders or unused languages or architectures, which does nothing more than free up some drive space. It will not make your Mac run faster or more efficiently, since having stuff stored on a drive does not impact performance, unless you're running out of drive space.
Mac OS X does a good job of taking care of itself, without the need for 3rd party software.
Your problem, and the OP's is a graphics problem, likely having to do with the screensaver, not a malware problem.
1
Dec 26, 2011, 08:13 AM
#5
UNCHeelYeah
macrumors newbie
Join Date: Dec 2011
Norton Antivirus, and what does it mean?
I suppose one reason I developed a concern that there was more here than meets the proverbial eye, so to speak was a message that I have received through Norton on multiple occasions. The last message of similar stated messages reads as follows (Norton Antivirus 2.2.1 (5) ): "Vulnerability blocked, December 13th, 2011, 8:57 P.M. When I click on "View Recent Activities", a window is opened that is titled "Activity Log." There, four columns are listed, titled from left to right "Date", "Event Type", "Result", and "Details." Under the December 13th episode, It lists "Portscan" under Event type, "Result" gives an IP Address (192.168.x.xxx), and "Incoming" under details.
I am admittedly a neophyte in the Mac world, having switched over from Windows 7 to Mac recently, but am intent on educating myself to the not-so-subtle differences. The above information that Norton displayed would lead one to believe that their antivirus software is protecting my iMac, and that its subsequent removal would have perhaps disastrous results ( i.e. - my iMac would be susceptible to said "Vulnerability", whatever it is, and that "Incoming would NOT be blocked). I had a conversation with Norton because previously, every time the stated "Vulnerability" attempted access, I was interrupted by a pop-up screen informing me of this. The Norton representative was able to turn off the pop-up screen notification, but stated that it would continue to log episodes of the "Vulnerability" when it attempted to portscan and access. So am I to understand that uninstalling Norton would leave my computer no less vulnerable to this vulnerability? It is confusing to me.
Furthermore, I suppose I did wonder if this vulnerability threat had anything to do with the issue of the black screen erasure with the mouse. I will attempt to post a picture of the screen as it was being erased with the mouse, and perhaps a short movie as well. As previously stated, I do not have a screen saver enabled. Thank you for your input, any information is helpful to me! _
~Marc
http://forums.macrumors.com/attachment.php?attachmentid=317412&d=1324905189
0
Dec 26, 2011, 11:19 AM
#6
gswilder
Thread Starter
macrumors regular
Join Date: Oct 2007
Ditto & FYI Workaround
UncHeel...
Thanks for posting the picture. It is same as my iMac problem. On my iMac, it happens 100% of the time. On my MBA, it happens randomly like yours.
I began to notice if certain programs were running, when it went into screen saver and sleep mode, this didn't happen. And when I woke it up, I got a message that said "could not be logged off due to Firefox or Sketchbook Pro, etc. So that got me to thinking. So....
Over the weekend, I disabled "logoff after xx minutes of activity" in system preferences. That seems to fix the issue. I still have it set to require a password after the screen saver/sleep mode kicks it. But I disabled the logoff toggle.
Still not sure what this is an issue, but seems to be a work around. I just want to make sure my iMac is still going into sleep with these new settings. Including the monitor sleep.
Any thoughts based on this new information?
Thanks again
Greg
0
Dec 26, 2011, 11:52 AM
#7
GGJstudios
macrumors G4
Join Date: May 2008
Quote:
Originally Posted by UNCHeelYeah
The above information that Norton displayed would lead one to believe that their antivirus software is protecting my iMac, and that its subsequent removal would have perhaps disastrous results
You have to remember that many antivirus apps consider cookies to be a "vulnerability" or "threat", when they're not. The only malware in the wild that can affect Mac OS X requires the user to actively install it. As long as a user is reasonably careful about where they get software, there is no need for 3rd party antivirus apps to protect Mac OS X from malware. Just make sure your firewall is enabled (System Preferences > Security > Firewall), and disable Java in your browser (Safari > Preferences > Security > Enable Java (uncheck))
Quote:
Originally Posted by gswilder
I just want to make sure my iMac is still going into sleep with these new settings. Including the monitor sleep.
You can let it sleep without logging off. That way, your apps/documents are still open when you wake it up, rather than having to relaunch apps and reopen documents. Recovery from sleep is much faster than from logging off.
0
Dec 27, 2011, 03:02 PM
#8
rda2w
macrumors newbie
Join Date: Oct 2011
Quote:
Originally Posted by gswilder
UncHeel...
Thanks for posting the picture. It is same as my iMac problem. On my iMac, it happens 100% of the time. On my MBA, it happens randomly like yours.
I began to notice if certain programs were running, when it went into screen saver and sleep mode, this didn't happen. And when I woke it up, I got a message that said "could not be logged off due to Firefox or Sketchbook Pro, etc. So that got me to thinking. So....
Over the weekend, I disabled "logoff after xx minutes of activity" in system preferences. That seems to fix the issue. I still have it set to require a password after the screen saver/sleep mode kicks it. But I disabled the logoff toggle.
Still not sure what this is an issue, but seems to be a work around. I just want to make sure my iMac is still going into sleep with these new settings. Including the monitor sleep.
Any thoughts based on this new information?
Thanks again
Greg
I have had the same problem on my mid-2010 iMac since upgrading to Lion and it's been driving me nuts. The relation to automatic Logoff makes sense to me now that I look at my settings. The logoff was occurring after sleep and it's the only thing I haven't tried yet. I had previously thought it was related to Sleep but it never occurs if I force it to sleep. It only occurs after the system was left unattended and went through it's normal steps of screensaver then sleep. I'll try disabling the automatic Logoff and see if it fixes the problem for me too.
-BA
0
Dec 29, 2011, 10:58 AM
#9
rda2w
macrumors newbie
Join Date: Oct 2011
Quote:
Originally Posted by rda2w
I have had the same problem on my mid-2010 iMac since upgrading to Lion and it's been driving me nuts. The relation to automatic Logoff makes sense to me now that I look at my settings. The logoff was occurring after sleep and it's the only thing I haven't tried yet. I had previously thought it was related to Sleep but it never occurs if I force it to sleep. It only occurs after the system was left unattended and went through it's normal steps of screensaver then sleep. I'll try disabling the automatic Logoff and see if it fixes the problem for me too.
-BA
I can only declare partial success with unpicking "logoff after xx". It solved the pixelated screen issue but now the computer is not sleeping. I guess I'll have to uncheck file sharing now.
-BA
0
Feb 6, 2012, 06:26 PM
#10
ougrad1764
macrumors newbie
Join Date: Apr 2010
Any updates?
Just wanted to see if there had been any changes since the last posting in this thread. I'm experiencing the same issue as OP on my 2011 13" MacBook Air w/ OS X 10.7.3, as well as on my parents' mid-2010 iMac (running OS X 10.7.2).
I can't seem to pin down the cause and have tried the steps suggested previously. Thanks!
0
Feb 21, 2012, 10:03 PM
#11
wchp
macrumors newbie
Join Date: Feb 2012
Still having the same issue here as well.
Have any of you tried a clean install of OSX?
Before I try a full reinstall I did an install on a external drive with no aps, just the bare install and I could not replicate the issue.
I continue to question if this is a graphics card firmware issue or and OS issue.
A reinstall (overlay) of the OS did not resolve the issue.
I have screen shots as follows:
1) Paint pixels on screen
http://i129.photobucket.com/albums/p227/wchp/iMac27%20Graphics%20Problem/photo1. jpg
2) Click Icon
http://i129.photobucket.com/albums/p227/wchp/iMac27%20Graphics%20Problem/photo2. jpg
3) Type in PWD
http://i129.photobucket.com/albums/p227/wchp/iMac27%20Graphics%20Problem/photo3. jpg
4) Logged in:
http://i129.photobucket.com/albums/p227/wchp/iMac27%20Graphics%20Problem/photo4. jpg
Last edited by grapes911; Feb 21, 2012 at 10:12 PM. Reason: replaced img with timg
0
Yesterday, 12:21 AM
#12
jrobin
macrumors newbie
Join Date: Feb 2012
Having the same issue
I have four MacBooks and a MacBook Air. I am seeing this issue on two MacBooks both running Lion 10.7.3. One is a newer i5 MacBook the other is an early 2010. The only common denominator I can think of is they are both set up with Parental Controls and they are set to logoff after X amount of time. The other MacBooks don't have this "pixel painting to revel the login screen issue" I also don't see it on our iMacs or the MacMini. Only the two with the issue are set to auto logoff. So the above poster is most likely on to something. I will give it a try by turning off the auto logoff on the two MacBooks in question. If that solves the problem then I will assume its a bug that needs to be addressed.
0
Yesterday, 12:30 AM
#13
ougrad1764
macrumors newbie
Join Date: Apr 2010
reinstall (overlay) of the OS did not resolve the issue
wchp - Thank you for following up and posting the screenshots. They match exactly what I was experiencing (and what UNCHeelYeah reported previously). I can confirm that I experienced the issue even following a clean reinstall of Snow Leopard on my MacBook Air (13-inch, Mid 2011).
jrobin - "I will give it a try by turning off the auto logoff on the two MacBooks in question. If that solves the problem then I will assume its a bug that needs to be addressed."
Good thinking! Thanks for taking the time to test with your machines. This will help provide further validation of what gswilder (OP) tried as well in reply #6. Interesting about Parental Controls, too.
Side note:
Since I recently joined the Apple Developers program, I did a clean install of SL on my MBA then upgraded via the App Store to Mountain Lion to "kick-the-tires" if you will. Interestingly, I've not yet experienced any issue related to waking from sleep with a black screen and pixilation, even while running all the same apps I had previously. I'll report here (and file a bug report with Apple) if I do see this issue pop-up in ML. I'll be reinstalling SL in a few weeks and will report back if/when the black screen and pixelation issue reappears. I'll be sure to note the applications left running at the time the computer went to sleep.
Last edited by ougrad1764; Yesterday at 12:44 AM. Reason: Follow-up to jrobin (reply came in while I was typing mine)
0
Yesterday, 09:04 AM
#14
evillanueva
macrumors newbie
Join Date: Feb 2012
I have experienced the same issue with my brand new MBA Late 2011.
I recently found out that this only happens when DISPLAY is set to go to sleep minutes before the "Log out after X minutes of inactivity". I had "Display sleep" option set to 5 minutes and "Log out after 10 minutes of inactivity" and this causes the display to go to sleep first (screen goes black) and then, 5 minutes later, it logs out.
If "Display sleep" is off and "Log out after X minutes of inactivity" is on, the issue does not replicate. So Im thinking it has something to do with the screen being black at the moment it logs out. Can you try and replicate that?
Thanks
0
Yesterday, 01:39 PM
#15
wchp
macrumors newbie
Join Date: Feb 2012
Quote:
Originally Posted by evillanueva
I have experienced the same issue with my brand new MBA Late 2011.
I recently found out that this only happens when DISPLAY is set to go to sleep minutes before the "Log out after X minutes of inactivity". I had "Display sleep" option set to 5 minutes and "Log out after 10 minutes of inactivity" and this causes the display to go to sleep first (screen goes black) and then, 5 minutes later, it logs out.
If "Display sleep" is off and "Log out after X minutes of inactivity" is on, the issue does not replicate. So Im thinking it has something to do with the screen being black at the moment it logs out. Can you try and replicate that?
Thanks
Just tested this premise and yes, you are correct.
IF: Screen saver ON after 5m AND require password immediately AND Sleep (Display) after 30m AND Logout after 60m I am able to reproduce the problem.
IF: Screen Saver ON after 5m AND require password immediately AND Sleep (Display) after 30m AND Logut after xx NOT enabled, problem goes away
IF: Screen Saver ON after 5m AND require password immediately AND Sleep (Display) OFF AND Logut after 60M enabled, problem goes away
So on my machine (iMac 27, 3.4/i7, 16GB/1333, Radeon 6970m/2048MB, OSX 10.7.3
It would appear that if I am running Monitor Sleep and it kicks in prior to LogOff then I am able to reproduce this artifact. Only Display sleep with immediate login OR Loguot should be used but not both.
The only other thing to test is is I leave display sleep on, and screen saver on but with NO immediate password and enable logoff if the problem goes away.
Testing for another day.
I have linked this entire thread to a Apple support ticket and will report back on Apples responseThank you so much wchp, this is brilliant. I have had this annoying problem for a long time. I eventually rang Mac support, they did not know how to fix the problem as you have suggested so they instigated many hardware replacements which eventually left my iMac severely crippled. They eventually replaced it with the latest model. But I spent two months working with a disabled computer which really interfere with my work.
Your solution appears to have solved my problem, at least so far, but I am hopeful that it is a permanent fix. I hope that your suggestions are taken up by Apple support. This may solve many users problems and avoid Apple making expensive fixes that don't actually work.
I thought that the new iMac would not have the 'Wake up from sleep by painting in the login window' problem but it did, this really annoyed me. Anyway now the problem appears to be solved, it's not I will repost and keep working on it. Thanks again. -
Auto Logout when idle not working for transaction iview
Hi,
When we open an SAP system using transaction iview and if the screen is idle for 30 mins, auto logout doesn't seem to be work.
We have verified that rdisp/gui_auto_logout parameter is set to 1800 i.e., 30 min. which a default value. Do we have to activate this service or its activated by default? Let me know if any other parameter needs to be configured.
Also, is there a way to detect multiple sessions when SAP transaction is executed like the way SAP Logon pad detects when user has logged in into SAP system on different PC?
We are using NW portal 7.01 and IE 7.
Regards,
VaibhavHi
the param icm/keep_alive_timeout does only that if within this time interval new data arrives over the network from the partner, the ICM attempts to keep the connection open once it has been established. If, for the existing connection, there is no further communication within the specified time period, the ICM terminates the connection. and this is a static param so if u change this it needs a sys restart and the param rdisp/plugin_auto_logout is also dependent on the above param as then it delets only the user context after the time period is reached not the work process context and the param login/disable_multi_gui_login works only for dialog log ins not for prta and as far as my knowledge there is no other way to detect this but i heard like by doing some code changes u can know something regarding that.
Thanks & Regards
Pradeep Srimanthula -
GXD:auto logout (maximum user idle time excedded)
Hi Gurus
I am connecting to an PI System and an R/3 System through AT & T dialler network. after logging into the systems, i am going through different scenarios and code in the respective systems. Till 15 to 20 minutes it working fine, afetr that i am getting the following error "GXD:auto logout (maximum user idle time excedded)" and "BDV:auto logout (maximum user idle time excedded)".
i have checked the profile parameetr instance "rdisp/gui_auto_logout" , In R/3 system it is given as 1800 and in PI system i do not have the authorization.
Please help me to resolve the issue.
I am working on client netowrk, shld i raise the issue with the basis Guys or it will be handled locally by the network guys.
Please help
Tahnking YouHi Arjun,
You can contact your BASIS/ADMIN team and ask them to increase the time interval for rdisp/gui_auto_logout so that your login will remain for long time.
Also check the link below for ref....
http://help.sap.com/saphelp_nw04/helpdata/en/22/41c43ac23cef2fe10000000a114084/content.htm
Thanks and Regards,
Naveen -
Hi,
Every half an hour or so I get automatically logged out of SDN.Its not like I am idle on SDN for that duration.Very much active.
It so happens that I am browsing forums..and suddenly the screen shows 'Guest..please login'(when i refresh) in top right hand corner of the screen.Or it shows 'You cannot post a reply unless u login' when I try to post a reply.
If I then click on HOME and goto home page..it comes up as if I am logged on.
Then clicking on forums..page comes up as GUEST..please log in.
Unless I click log off and come back to home page and login again,this does not get corrected.Its irritating sometimes.
Some of my colleagues too seem to experience this.
Is it fairly common bug?
cheers,
Vishvesh
Message was edited by: VishveshThanks Eddy.
I hadnt seen your blog.Its very informative.I got some idea about this auto logout problem.
But shouldnt the user be auto logged-out only when he is idle for the duration?I thought so..
Also..u have mentioned this too..being logged off from forums but still logged on on the home page(PORTAL).
What is the purpose behind this revoking mechanism?Reduce traffic/load on servers?
cheers,
Vishvesh
Maybe you are looking for
-
any help would be nice!
-
I bought a bluetooth headset because I heard it would make a doog microphone for my mac mini and after I paired it it worked fine and now all of a sudden it's not working anymore. I tried pairing it again and the pairing was successful but when I sel
-
SQL Developer hangs when expanding table node
Hello All, One of my schemas has 3035 tables. When I expand the "Other Users" node, then the schema owner, then expand "Tables", SQL Developer hangs. I have allowed it to run (as it indicates it is working) for 45 minutes, but it never returns. I hav
-
Fields for Selection on selection screen - Data Dictionary
Hi, I have an issue while selecting the required fields for selection on the Standard table. VBAK --> Settings > Fields for Selection> Select required fields and save it as a variant. It looks good for that day but it again changes to the standard se
-
TS1368 Purchase of Office 2010 from app stroe
I recently purchase this office 2010 app from the app store. IT IS IN RUSSIAN A LANGUAGE I DO NOT SPEAK. i would like a credit please Your receipt No.158039544378