Python keeps crashing while using Tamper

[seyDoggy]

Python keeps crashing, see the two malloc breaks:

2014-11-18 13:24:26.000 kernel[0]: process Python[19764] caught causing excessive wakeups. Observed wakeups rate (per sec): 386; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45001
2014-11-18 13:24:27.615 spindump[852]: Saved wakeups_resource.diag report for Python version 2.7.8 (2.7.8) to /Library/Logs/DiagnosticReports/Python_2014-11-18-132427_mbp13-2.wakeups_resource.diag
2014-11-18 13:36:08.000 kernel[0]: process Python[19814] caught causing excessive wakeups. Observed wakeups rate (per sec): 383; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45240
2014-11-18 13:36:09.566 spindump[852]: Saved wakeups_resource.diag report for Python version 2.7.8 (2.7.8) to /Library/Logs/DiagnosticReports/Python_2014-11-18-133609_mbp13-2.wakeups_resource.diag
2014-11-18 13:42:26.000 kernel[0]: process Python[19852] caught causing excessive wakeups. Observed wakeups rate (per sec): 389; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45046
2014-11-18 13:42:27.240 spindump[852]: Saved wakeups_resource.diag report for Python version 2.7.8 (2.7.8) to /Library/Logs/DiagnosticReports/Python_2014-11-18-134227_mbp13-2.wakeups_resource.diag
2014-11-18 13:52:19.405 Python[19852]: Python(19852,0x10ec80000) malloc: *** error for object 0x7fc5342a8cb8: incorrect checksum for freed object - object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug
2014-11-18 13:52:19.975 ReportCrash[19895]: Saved crash report for Python[19852] version 2.7.8 (2.7.8) to /Users/adam/Library/Logs/DiagnosticReports/Python_2014-11-18-135219_mbp13-2.crash
2014-11-18 13:54:17.000 kernel[0]: process Python[19902] caught causing excessive wakeups. Observed wakeups rate (per sec): 388; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45218
2014-11-18 13:54:17.875 spindump[852]: Saved wakeups_resource.diag report for Python version 2.7.8 (2.7.8) to /Library/Logs/DiagnosticReports/Python_2014-11-18-135417_mbp13-2.wakeups_resource.diag
2014-11-18 14:02:04.000 kernel[0]: process Python[584] caught causing excessive wakeups. Observed wakeups rate (per sec): 388; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45087
2014-11-18 14:02:05.381 spindump[599]: Saved wakeups_resource.diag report for Python version 2.7.8 (2.7.8) to /Library/Logs/DiagnosticReports/Python_2014-11-18-140205_mbp13-2.wakeups_resource.diag
2014-11-18 14:06:20.000 kernel[0]: process Python[613] caught causing excessive wakeups. Observed wakeups rate (per sec): 387; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45107
2014-11-18 14:06:20.973 spindump[599]: Saved wakeups_resource.diag report for Python version 2.7.8 (2.7.8) to /Library/Logs/DiagnosticReports/Python_2014-11-18-140620_mbp13-2.wakeups_resource.diag
2014-11-18 14:29:35.000 kernel[0]: process Python[876] caught causing excessive wakeups. Observed wakeups rate (per sec): 394; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45088
2014-11-18 14:29:35.783 spindump[599]: Saved wakeups_resource.diag report for Python version 2.7.8 (2.7.8) to /Library/Logs/DiagnosticReports/Python_2014-11-18-142935_mbp13-2.wakeups_resource.diag
2014-11-18 16:23:20.445 Python[876]: Python(876,0x105c16000) malloc: *** error for object 0x7fc3ca9a5d50: pointer being freed was not allocated
*** set a breakpoint in malloc_error_break to debug
2014-11-18 16:23:20.935 ReportCrash[1499]: Saved crash report for Python[876] version 2.7.8 (2.7.8) to /Users/adam/Library/Logs/DiagnosticReports/Python_2014-11-18-162320_mbp13-2.crash
2014-11-18 16:25:17.000 kernel[0]: process Python[1506] caught causing excessive wakeups. Observed wakeups rate (per sec): 390; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45194
2014-11-18 16:25:17.995 spindump[599]: Saved wakeups_resource.diag report for Python version 2.7.8 (2.7.8) to /Library/Logs/DiagnosticReports/Python_2014-11-18-162517_mbp13-2.wakeups_resource.diag

[dutzi]

TBH I don't even know how to start debugging this... I'm not so familiar with Python.

Is this a log file maintained by Python? How long after running tamper did you get this error? (Assume tamper starts running the when Chrome loads up)

Maybe Tamper's Chrome extension's log will tell us more? Could you please do the following:

• Browse to chrome://extensions/
• Check "Developer Mode" on
• Look for Tamper, click the "background page" link
• Go to Console
• Click Cmd+R

And copy & paste the console messages here?

[seyDoggy]

How long after? Can't say atm since I can't reproduce right now.

connecting to proxy
background.js:1 Got message:  Object {method: "hello"}
background.js:1 Got message:  Object {version: "0.24.1", method: "version"}
background.js:1 Mitmproxy Extension Version: 0.24.1
background.js:1 Proxy Log: Starting proxy... (8888)
background.js:1 Got message:  Object {method: "start-proxy", port: "8888"}
background.js:1 Got message:  Object {rules: Array[2], method: "update-rules"}
background.js:1 Got message:  Object {method: "proxy-started"}

[dutzi]

I mainly wanted to see if there are a lot of random disconnects between the Chrome extension and the Python one, but it looks like it's running fine.

[saalmaan]

@dutzi I have got two system crashes today and each time I investigated it was python crashing, I will report back with full system log

[dutzi]

@saalmaan, did you experience any crashing lately? @seyDoggy, where do you see this log file?

[seyDoggy]

I haven't been using it all that much.

On Fri Dec 12 2014 at 8:24:54 AM Eldad Bercovici [email protected] wrote:

@saalmaan https://github.com/saalmaan, did you experience any crashing lately? @seyDoggy https://github.com/seyDoggy, where do you see this log file?

— Reply to this email directly or view it on GitHub https://github.com/dutzi/tamper/issues/15#issuecomment-66771770.

[saalmaan]

I havent see any crashes lately and that is may be due to the fact that I am also not using tampre not that much, I will report back if I see any issue, lets keep this issue open for moment.