I'm very sorry to hear about the trouble you had. This is the first time this issue has surfaced for anyone as far as I know.

In your review, you mentioned that your site has over 1000 pages. That may be related to the problem. I'll try to reproduce the error and record benchmarks while increasing the number of pages of my test site to a comparable scale.

Any other information you could provide would be helpful, such as:

- When did your system hang? (e.g. during install, when clicking the Cobble button, or running a specific query)
- What version of Cobble did you install? Based on the timing of your posts, I'm assuming it is version 1.13
- What is your webhosting environment?

Add-on Installation was ok but
It hang after I clicked the Add-on button in the dashboard.

I installed the last version.

My website environment is:http://www.kawonga.com/phpinfo.php...

Thanks for that info, that helps a lot. From your phpinfo(), PHP has a max execution time of 30 seconds and MySQL has a connection timeout of 60 seconds -- but it sounds like from your post, that the process exceeded these limits somehow...

Did any PHP errors show up in your server logs?

I checked my error log and nothing related to the time I execute your add-on.

I wish I can give you more details but I received no visual errors. I did reboot apache service after 5 min to quickly kill the process because it was not responding.

Thanks for checking the logs! I'll see what I can figure out. The 'Cobble' button on the dashboard is basically just running a number of SQL queries and reading some directory and file contents (pretty generic stuff). It seems that the script should either a) work correctly, b) throw a php exception or c) hit the 30 second PHP timeout.

Anyway, I'll be sure to PM you if I can reproduce and fix the problem.

Edit: You said you can't remove it anymore-- What happened when you tried uninstalling the package?

I tried putting the code that refreshes the cobble tables inside an infinite loop. After 60 seconds, PHP quit with the message: "Fatal error: Maximum execution time of 60 seconds exceeded..."

That's sort of interesting, since my max_execution_time is set in php.ini as 30 seconds. The max_input_time is set as 60 seconds, however.

max_execution_time is defined simply as "Maximum execution time of each script, in seconds"

max_input_time is defined as "Maximum amount of time each script may spend parsing request data"