wvengen

Finding a Ruby memory leak using a time analysis

When developing a program in Ruby, you may sometimes encounter a memory leak. For a while now, Ruby has a facility to gather information about what objects are laying around: ObjectSpace.

There are several approaches one can take to debug a leak. This discusses a time-based approach, where a full memory dump is generated every, say, 5 minutes, during a time that the memory leak is showing up. Afterwards, one can look at all the objects, and find out which ones are staying around, causing the

ravinsharma12345

//Display Fields
add_action( 'woocommerce_product_after_variable_attributes', 'variable_fields', 10, 2 );
//JS to add fields for new variations
add_action( 'woocommerce_product_after_variable_attributes_js', 'variable_fields_js' );
//Save variation fields
add_action( 'woocommerce_process_product_meta_variable', 'variable_fields_process', 10, 1 );

function variable_fields( $loop, $variation_data ) {
?>	
	<tr>

ravinsharma12345

/**
 *   Determine if a post exists based on post_name and post_type
 *
 *   @param $post_name string unique post name	
 *   @param $post_type string post type (defaults to 'post')
 */

function post_exists( $post_name, $post_type='post' ) {
	global $wpdb;

aaronshaf

All Things JavaScript

Concepts

• this
• bind
• Hoisting
• Operator Precedence
• Lambda
• Object literals
• Prototypical inheritance vs. classical inheritance